When developer Tim Walpole contacted us to showcase his new Snipcart integration, we thought: “Woah, this is cool, gotta do something with this!”
Tim went down the JAMstack road and used tools we’ve been writing about to build a neat Gatsby progressive web app (PWA) for his client INGMARSON.
He was kind enough to give us his take on this modern way of building websites and how Snipcart fits into all of this.
It was a pretty exciting exchange, so let’s see what he had to say!
[Interview excerpt]
We're big proponents of the JAMstack at Snipcart. Do you know about it & (if so) how do you feel about it (JavaScript, APIs, Markup)? Thoughts, doubts, experience?
As a small (growing) company owner, Robert wants to be able to concentrate on what is important—delivering high quality, ethically sourced clothing designs. We don’t want to have to worry about maintaining a high-cost website, ensuring security, staying up-to-date, or meeting GDPR regulations for data storage.
When I researched how to check all these boxes, I came across posts from Snipcart (and others), showing how JAMstack could do that. With it, we could run a static website, with markdown content which was rebuilt every time the content is changed. We could use a simple CI/CD pipeline to push content through development, staging and live servers allowing us to validate both technical and content changes before they go live. It was a revelation.
→ Read the full post here
Top comments (1)
Hi Charles.
This looks like a good post here. Can you share this in full on DEV?
DEV generally asks that folks share their posts in full if possible and there is tooling provided (dev.to/settings/publishing-from-rss) to make it so that it's relatively easy to repost from outside blogs.
Hope you'll consider sharing the full post going forward.