I am building a festival webshop where users can buy camping tickets for multiple festivals. At the moment I’m using a cached collection to bypass the strict rate limit on the API I’m using.
SEO is very important for this project of course. That’s why I’m thinking about changing the cached collection to a static so every festival page can have it’s own SEO tags.
The problem with this is that it will be too much work for our customer to refetch the collection and publish the application every time something minor changes in the backend. Is there a solution for this? Is already came across the weweb Server API where it should be possible to publish the application with an API call. This would already help us out partially. The static collection should be refetched as well in this case… Can this also be done via an API call or is this done automatically when publishing? Any other suggestions?
So I checked and it is indeed possible on an enterprise plan because of the cost attached to publishing a project with pre-rendering.
That said, if pre-rendering is not essential for your project, you could get great results with a dynamic collection. If you’re interested, we are running a closed beta on a small number of projects to add SEO tags on dynamic collection pages.
