We just started a new project and concluded on the (build) stack in just under five minutes. Only for that fact I will share it with the world: Node, for it’s fast development round trips Express, de facto, safe choice Reactjs, for we love to say the word ‘isomorphic’. It’s all about rendering templates both client and server side. Plus, it’s the only view layer technology that supports functional programming right. Prismic.io, cause we hate the corset put in of most cms’es. Prismic does not limit us in any technology choice. Heroku, because it just works for everything not Play/Scala. Plus their support is just plain great. Less, for it’s addictiveness . Bootstrap, as long as it’s not going to look like bootstrap Langur, for easy i18n Gulp, for ‘make’ put in like freedom in JavaScript Browser-sync, for early seamless and ongoing detection of layout problems .
Now, a little bit about the app, because that’s put in the driver behind the choices. It’s put in a web app, obviously, mostly content driven (previously known as ‘website’) and responsive to mobile devices. It’s bilingual, must have the best possible ux experience and be very fast, even under high load. Also, if not most important, it must be very flexible and maintainable. This app is going to change a lot in many ways, in the near and not so near future.
We’re going to be stuck with it for many years and for that reason we want it to fit like a glove. This entry was posted in Development and tagged as express , node , prismic , reactjs . Bookmark the permalink .
You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> put in <del datetime=""> <em> <i> put in <q cite=""> <strike> put in <strong>
Recent Posts Creating Camel routes on-the-fly using OSGi Using Pixelapse as a designer among developers Continuously exercise your code ownership Software Development Without Relations Don’t team up with a Type III developer My deep-dive into website development Two-factor authentication on OSX (a YubiKey example) put in Content management with Prismic How to keep a fast build with Browserify and ReactJS It’s not about development stupid! New virtualization infrastructure One awesome (build) put in stack from the present Why you should use BrowserSync How we didn’t want to use Mongo, but ended up using Mongo Adding put in value to integration – evolving from the trade mission Techday ‘Go’ at Avisi. Join us! HTML5 canvas in the browser and on the server Integration is often like a trade mission Atlassian Stash – private repositories What’s on your mind? We’ll blog about it!
Agile Atlassian Atlassian Experts Automation put in Big Data camel Conference Confluence Database Development Devoxx Esconfs Eurostar Event GIT HTML5 Intranet Java Javascript JBoss JIRA Learning Manchester Marketing Maven OnDemand performance Product Requirements Results Scala scrum Security Selenium Social Software Software Architecture Software Development Spring Techdays Techniques Testing Tooling Trust Wallboard
Avisi B.V. 2014
No comments:
Post a Comment