You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the sitemap.xml is generated on build time. This is cool for an static website where you have to prebuild all website. However, sometimes our sites are dynamic. For example a blog where you are using a CMS. It would be lovely that the sitemap.xml is dynamic and can fetch data from the outside to align dynamic pages created on the fly. Currently you will have to rebuild the project.
Describe the solution you'd like
I would love the sitemap to be static if we output brisa with as an static site. Or dynamic in the scenario where brisa has available a server.
sitemap builds in 0.02s at most in most case scenario. Let's say you have an API fetch to do and take 1s. The impact on performance is irrelevant as robots will wait for it and impatient humans won't be affected. Also, the user will be able to add a cache if consider it necessary.
Describe alternatives you've considered
Just rebuilding the site with every backend change, but is a waste of time and resources.
The text was updated successfully, but these errors were encountered:
aralroca
changed the title
Proposal: Sitemap should be flagged as dynamic or static, depending on brisa output.
Generate Sitemap beyond static for dynamic routes
Mar 8, 2025
Is your feature request related to a problem? Please describe.
Currently the sitemap.xml is generated on build time. This is cool for an static website where you have to prebuild all website. However, sometimes our sites are dynamic. For example a blog where you are using a CMS. It would be lovely that the sitemap.xml is dynamic and can fetch data from the outside to align dynamic pages created on the fly. Currently you will have to rebuild the project.
Describe the solution you'd like
I would love the sitemap to be static if we output brisa with as an static site. Or dynamic in the scenario where brisa has available a server.
sitemap builds in 0.02s at most in most case scenario. Let's say you have an API fetch to do and take 1s. The impact on performance is irrelevant as robots will wait for it and impatient humans won't be affected. Also, the user will be able to add a cache if consider it necessary.
Describe alternatives you've considered
Just rebuilding the site with every backend change, but is a waste of time and resources.
The text was updated successfully, but these errors were encountered: