Professional web developer and hobbyist programmer from the Welsh Marches. I'm particularly interested in performance, accessibility, and reducing carbon emissions from software.
I think it really depends on the kind of content on the site. Static sites will always be faster than those generated on request via a server side language. Some kind of CMS (I know there are a few out there already) will be essential for wider adoption though, if non-technical users are told they have to learn git and markdown to update content on their site they will go with something like Wordpress instead.
I am slightly wary of the JAMstack for dynamic content; it's not something I've really explored much (I'm more comfortable with HTML and CSS than JS), but any system that explicitly requires JS to fetch content seems inherently less robust to me - I think all the primary content on a page should be rendered server side by default with dynamic JS as a progressive enhancement.
Having said all that, my own personal blog / portfolio site is hosted on Netlify and built using Zola and I absolutely love the control over markup this gives me vs a CMS based system, and the convenience vs hand coding every page, It seems to be the best of both worlds.
Professional web developer and hobbyist programmer from the Welsh Marches. I'm particularly interested in performance, accessibility, and reducing carbon emissions from software.
I can't actually think of any off the top of my head. If you could only re-render pages where stock / price etc. has changed you could extend the definition of static to things that only render when changed.
I suppose the only things that would need to be truly dynamic would be situations like unique account pages and stock prices etc?
Very interesting when you start to think about what can be rendered statically.
Social media is an example of a website with dynamic content and Ebay is an e-commerce example; they all have data that is changing constantly. They wouldn't work well as JAMStack as you'd have to trigger a rebuild every time someone makes a bid or creates an auction.
That's not to say you can't have the best of both worlds. Almost every application I've built in the passed two years has made use of SSR and Static.
I think it really depends on the kind of content on the site. Static sites will always be faster than those generated on request via a server side language. Some kind of CMS (I know there are a few out there already) will be essential for wider adoption though, if non-technical users are told they have to learn git and markdown to update content on their site they will go with something like Wordpress instead.
I am slightly wary of the JAMstack for dynamic content; it's not something I've really explored much (I'm more comfortable with HTML and CSS than JS), but any system that explicitly requires JS to fetch content seems inherently less robust to me - I think all the primary content on a page should be rendered server side by default with dynamic JS as a progressive enhancement.
Having said all that, my own personal blog / portfolio site is hosted on Netlify and built using Zola and I absolutely love the control over markup this gives me vs a CMS based system, and the convenience vs hand coding every page, It seems to be the best of both worlds.
Does anyone have an example of a website with dynamic content, e.g. with production product prices changing many times per hour etcc ?
I can't actually think of any off the top of my head. If you could only re-render pages where stock / price etc. has changed you could extend the definition of static to things that only render when changed.
I suppose the only things that would need to be truly dynamic would be situations like unique account pages and stock prices etc?
Very interesting when you start to think about what can be rendered statically.
Social media is an example of a website with dynamic content and Ebay is an e-commerce example; they all have data that is changing constantly. They wouldn't work well as JAMStack as you'd have to trigger a rebuild every time someone makes a bid or creates an auction.
That's not to say you can't have the best of both worlds. Almost every application I've built in the passed two years has made use of SSR and Static.
And what would you choose from assistance such as gatsby but to build a mainly dynamic website?
SSG is not recommended where content is dynamic. you should go with SSR instead