The rise of the Jamstack methodology represents an ideological shift in how websites are built, deployed, and maintained. See why we’ve shifted to a model of static-site generation.
Aging software turns into technical debt. Jamstack means that the single dev who originally built it, is not the only one who can fix it.
Smartphone adoption has made speed the top priority. Jamstack means faster loads with less latency and more cacheability.
Monolithic apps are complicated and have single points of failure. Jamstack cuts complexities and dependencies.
Dynamic applications need routine maintenance to remain operable. Jamstack means we can avoid that kind of stress.
We love the Jamstack so much we can’t keep it to ourselves. That’s why you can find us talking up its benefits at conferences. Here’s where we’ve been lately:
With a new CMS popping up almost weekly, how do you choose the right one? You have to consider cost, editing experience, front-end integrations, and so much more. Let's find out with Ample’s Director of Technology, Sean C Davis.
Becky Blank, Ample’s Director of Technical Operations, facilitates a client-focused discussion with examples of success and common pitfalls.
Taylor MacDonald, Ample’s CTO, presents a lightning talk that helps you avoid disaster, using a gradual migration strategy.
Crossroads is a church for people who don’t like church. They’re also the fastest growing church in the U.S. They need a high-performing, future proof site that can grow, and grow.
“Our job is in part education. What benefits will this bring? What does it mean to deploy a static site? What’s the effect on the current architecture and how do we get there? Ample was able to translate all of this and in turn, deliver a solution that ticked all the boxes in speed, performance and security. Plus it simplified the code base, allowing them to staff their dev team more effectively.”
– Taylor MacDonald, Ample CTO
Without the Jamstack methodology, when you type in a site URL, your browser asks the web server for content. That web server communicates with an application server running an application like Drupal or WordPress. It connects to a database, runs the content through HTML templates, and then returns the resulting HTML to your browser.
Sound complicated? That’s exactly what it is. Also, this complexity makes your site slow and vulnerable to security breaches.
With the Jamstack, all the dynamic work was performed during a build process. When you type in a Jamstack site URL in your browser, all your browser will have to do is download an HTML file.
That’s not complex. It also makes your site both fast and risk averse.
Follow our journey as we continue to build better and better sites using this methodology.
Sign up for our email newsletter. Nothing spammy about it. Just a monthly rundown of what we’re sharing.