It’s the beginning of summer season here in the U.S., so welcome to the Summer of JAM! We’ve had some discussions in the New Dynamic Slack lately about just what is and isn’t JAMstack and where the space is going as awareness explodes, the ecosystem expands and new use-cases are explored. I doubt we’ll come to a conclusion on that anytime soon, but one thing we do agree on is that the landscape for web development is forever changed.
“Over the next 5-10 years, the vast majority of web sites/apps will migrate to a cloud-native web framework”
What is a headless (or decoupled) CMS 2. Why use WordPress as a headless CMS 3. Tools and process of building a headless site 4. A basic example and some gotchas we found 5. The Future is (probably) headless
Continuous Delivery & Integration for Java, .NET apps in AWS, GCP, Azure, Bare Metal. DevOps teams can quickly, safely, and securely deliver their applications into production. Click here to learn more and get early access.
Contentful is a really powerful CMS that we use on a number of projects at The Couch. However despite most of our clients having an intimate hate for Wordpress, they do have an intimate love for some of the common features. One of which isn’t something that works out of the box with Contentful: Preview.
At CloudCannon, we’re always looking for ways to offload content management from developers and empower editors to make changes themselves. Enabling editors to build their own pages with complex elements such as slideshows, testimonials and call to actions is something we’ve wanted to support but haven’t had a good solution for.
The latest maintenance release for Publii, version 0.34, is released and ready for download. As with all maintenance-oriented releases, the focus here has been on bugfixes and more minor or backend improvements, but there’s a few new features…