Hi everyone,
I have been testing a workflow for repeatedly publishing small static HTML pages generated with AI tools.
One question I keep running into is how each page should map to Netlify:
- Create a new Netlify site for every generated page
- Reuse one site and replace the current deployment
- Let the user select an existing site before deployment
Creating a new site provides a clean URL for every page, but it may create too many unused sites over time. Reusing an existing site is simpler, but users could accidentally overwrite a page they still need.
I am also experimenting with a browser extension (HTML Deployer) that previews the HTML before sending it to Netlify. Before continuing with the integration, I would appreciate feedback from people who manage many small static deployments.
Which approach would you expect from this type of workflow?
Are there API limits, site management issues, or deployment details that should be made especially clear to users?
Disclosure: I am developing the browser extension being discussed. My goal with this post is to understand the most appropriate Netlify workflow rather than promote the extension.