A stable front-end stack for 2016

We’ve been trialing new front-end tools and libraries over 2015 but our main stack has remained very stable. Starting a new project? Here are Springload’s picks, all available in our front-end starter kit.

Shiny JavaScript tools

We prefer our JavaScript written using ES6/ES2015. While still very new, it alleviates a lot of JS pain points and is here to stay. Browser support is growing fast, and in the meantime Babel can take care of the compilation.

For libraries, we are big fans of React. Its developer experience is great, and it makes you think about your UI at a higher level of abstraction. Like Web Components, but actually usable now. No need for Flux and its dozens of implementations to benefit from it.

Regardless of how the front-end code is written, it will be processed by a Node toolchain – Gulp, Browserify and ESLint are all very stable. Focus on writing code while linting, minification and live-reloading are taken care of.

Battle-tested preprocessors

Our technical lead always says that what matters with CSS is not how you write it but how you architect it. We are frugal users of Sass, relying on a small set of language features and avoiding the most powerful (and dangerous) ones. Instead of tooling, we follow the principles of BEM, OOCSS, and Harry Roberts. Have a look at inuitcss for a taste of it.

While not in use yet, we are quite excited about things like CSS modules. As CSS tooling becomes more powerful, PostCSS and Webpack’s CSS loader are interesting pieces of technology to watch. In the meantime, leverage the best of PostCSS by adding Pleeease to your toolchain. It’s very easy to drop in and includes autoprefixing, old browser fallbacks and minification in one convenient package.

Built on the shoulders of giants

Django is our preferred web framework. It’s very pragmatic, and has a good level of abstraction while giving access to the details when necessary. It does modules and code reuse very well with its concept of apps. And the Python community is thriving.

Springload’s CMS of choice is Wagtail. It offers a great content-editing experience out of the box, and its architecture makes it easy to create new administration features or tailored components. Haven’t heard of it before? Have a look at Wagtail’s StreamField concept and you won’t want to use Drupal’s regions ever again.

Wagtail’s StreamField is a mechanism to create free-form content by combining and reordering content patterns.

One year ago we discussed our reasons for going with Wagtail as our CMS. Today, I am happy to say we now regularly contribute to its codebase and specific plugins.

Tech to be excited about this year

JavaScript Fatigue doesn’t have to be a thing after all. While the pace of innovation is high, great open-source software is emerging, and improving the way we work. The web platform is getting better by the minute and there is no sign of it stopping. To get you pumped up for the year to come, here are three things to get excited about in 2016:

For 2016 we wish you a happy, pragmatic, stable front-end stack. If you want to learn more about our choices, go have a look at our starter kit.