Each Cloudron app instance manages exactly one website.
JRH BLAH
This starter keeps TinaCMS, Next.js, content files, media uploads, and MongoDB-backed indexing inside one Cloudron app while preserving Cloudron's read-only and read-write filesystem boundaries.

Content lives under persistent storage and is editable without rebuilding the package.
MongoDB is used for Tina's production datalayer cache because Tina's documented production adapters currently support MongoDB and Vercel KV, not PostgreSQL.
Uploads and writable content are kept out of /app/code and served through Dockerfile-created symlinks into /app/data.
A packaged editing workflow that respects Cloudron constraints.
The starter separates packaged code from writable site content, so editors can keep working after install without modifying the immutable application image.
What this starter gives you
Editors manage pages, menus, footer content, SEO defaults, and a small theme layer instead of raw repo files.
Uploaded images land in persistent storage and are available for page sections and SEO images.
The Pages collection includes in-app search so larger sites remain manageable in the Tina admin.
What editors like about it
A few example testimonials to show the structure and layout of this block.
Editing the site feels much less technical than changing source files.
I can update text, images, and page sections without needing a developer for every small change.
Frequently asked questions
This example FAQ section shows how common questions can be grouped on a page.
Do I need to know code to edit the site?
No. The editing interface is designed so that a non-technical user can manage pages, images, and common site settings from the browser.
You can use bold text for emphasis and markdown links such as About.
Can I add these blocks only where I need them?
Yes. Each block is added as a page section, so you can place it only on selected pages and choose the order.
- Add a block only where it helps
- Reorder blocks to change page flow
- Keep each page focused
Start with a brochure site and expand carefully.
This first functionality set focuses on a strong foundation for site pages, navigation, footer content, SEO defaults, and simple theme tokens.