5 ms·
I don't know if I have a "JAMstack", but here's my tooling to create a product marketing site: - GitHub for version control - AWS CodePipeline for building an
by hmak 8y ago
I don't know if I have a "JAMstack", but here's my tooling to create a product marketing site:
- GitHub for version control
- AWS CodePipeline for building and deployment (include cache invalidation)
- NextJS to statically export my site built in React
- S3 to host my content
- Cloudfront as my CDN
- Route53 to manage my domain (that I got from Google Domains)
- API's are hosted on a different stack
I didn't use a service like Netlify because I wanted to reduce the number of vendors that had access to my user's data (like IP address etc. etc.)
- valtism 8y agoThis is pretty much exactly a JAMstack, provided you keep your content in some separate markup. Static site generation had an image problem, because people thought that having a static site meant that they would not be able to have dynamic content on their site. JAMstack is basically a way of rebranding static sites saying that you should generate the pages you are serving and push them to a CDN edge network for TTFB speed, but you can still make them dynamic by using API calls to anything that needs to access a DB, etc. It's a way of showing people that we should be doing more things statically when we can, and separating out dynamic components into their own APIs.