https://next.smashingmagazine.com/2017/03/a-little-surprise-is-waiting-for-you-here--meet-the-next-smashing-magazine/ Smashing Magazine is changing: a new design, a new layout, a new technical stack, a new printed magazine, a new Smashing Membership, and the same good ol’ obsession with quality content. Here’s a sneak preview of what’s coming up.
- jamstack - https://www.smashingmagazine.com/2016/08/using-a-static-site-generator-at-scale-lessons-learned/
- Netlify CDNs - https://www.netlify.com/
- GoCommerce - https://github.com/netlify/gocommerce A headless e-commerce for JAMstack sites
- Git Based CMS (Netlify's open source git cms) - https://www.netlifycms.org/
- Real time search with Algolia - https://www.algolia.com/
- HTTP/2 support
- Progressive web app (service worker toolbox library) - https://github.com/GoogleChrome/sw-toolbox
Bye WordPress, Hello Hugo! - http://gohugo.io/ Introducing Hugo, a new idea for making website creation simple again. Hugo works flexibly with many formats, and is ideal for blogs, docs, portfolios and much more. Hugo’s speed fosters creativity—it makes building a website fun again.
Hugo is a general-purpose website framework. Technically speaking, Hugo is a static site generator. Unlike other systems which dynamically build a page every time a visitor requests one, Hugo does the building when you create your content. Since websites are viewed far more often than they are edited, Hugo is optimized for website viewing while providing a great writing experience.
- Written in Go https://golang.org/
- Fast & Modern Static Website Engine
- Hugo is developed with spf13 (Steve Francia) and Friends
- Make the Web Fun Again
- Scripst to convert/import your existing posts - https://gohugo.io/tools/
Why the change? (from the post) In the past, we were using WordPress as a CMS, our job board was running on Ruby, and at one point we switched to Shopify from Magento for our online shop. Not only was maintenance of four separate platforms incredibly complicated, but designing a consistent, smashing experience the way we envisioned it proved to be nearly impossible due to technical restrictions or requirements imposed by these platforms.
Indeed, developing for every platform separately was quite expensive and slow, and in many ways, creating a cohesive experience where a user would literally “flow” from one area to another was remarkably difficult. As a result, because some areas were more important from the business perspective, they were growing and evolving fast, while the others were decaying in the dark. This led to an inconsistent, incosehive, and, frankly, quite annoying and frustrating experience. And even once we’ve committed to make some major changes to unify the experience, it turned out to be a big, challenging undertaking since we were using different platforms, stacks and at some point even different designs.
A trend, moving away from WordPress - Still a great framework, but other alternatives - Craftcms https://craftcms.com/ (see Craft 3 https://craftcms.com/3) - https://webflow.com/ (Design, develop, host and CMS)