Static export for self-hosting: Generating pages from CMS data or a "no dynamic pages" limitation?
Static export for self-hosting: Generating pages from CMS data or a "no dynamic pages" limitation?
At a glance
The community members are discussing the limitations of the Static Export feature for self-hosting. The main points are:
- During the build process, resources are fetched but dynamic URLs are unknown, so only resources that don't depend on routing will work on the static pages.
- There is potential to improve this, but the community wants to see the demand for it first.
- Some community members feel that turning everything dynamic into static is a bit backwards, as the platform is built for dynamic sites.
- However, others think this feature would be useful, even for "archiving" projects, and mention a tool that can do something similar for Webflow.
There is no explicitly marked answer in the comments.
Does the Static Export for self hosting run a build that would generate pages based on CMS data or is that the "No Dynamic Pages" limitation mentioned? I would just assume that it would run a build and output a static page from that and that it just wouldnt be SSR so no dynamic upates to those built bages, but wanted to get some clarity
I think this feature would be very useful. Even for "archiving" projects. For webflow there is a hack that can do something like that https://webflow-exporter.sktch.io/