re: How do you convince a client to a static website? VIEW POST


I recently moved a bank from sitecore over to netlify, algolia, contentful using Gatsby and react.

The biggest selling point? Cost, security and flexibility.

Moving to jam stack offers huge potential for the future I reviewed all of the architecture patterns and with the bank wanting their content produced once but available anywhere it made real sense to move away from a tightly coupled traditional CMS.

One huge benefit of headless and the JAM stack is the incremental movement you can make.

We started out using just the static website and blog posts, product info and other content was all produced in markdown files. This got us to a point of replicating what we had without needing sitecore. It was also insanely fast without any database connections and Gatsby handling the build.

After that we added in contentful and removed the markdown where appropriate.

code of conduct - report abuse