I use Strapi Single Types for individual, one off web pages on my site. They provide a clear mechanism for showing what static pages I have and make editing them easy. So far, all my pages have the same fields and are based on 2 components and 1 relation:
To add a new page, I need to create it in my development environment as a new Single Type, commit the change, push it and wait for Heroku to pick up the change and build the new commit. I use the Content-Types Builder to do this. The Content-Types Builder is not available in production, hence new content types are build in a developer environment.
For a commercial deployment, this can present a problem - only developers can create new pages. As content managers need to add or remove pages, this inserts developers into the content management pipeline. Content managers cannot make these changes on their own. Only existing pages can be modified.
The best solution I can see to this is to create a Pages Collection Type. Provided all pages possess the same structure (as I have), this would mean that content managers can create or delete pages as required.