Introduction
SAWTEE’s website is a Laravel + Inertia + React application with two surfaces:
| Surface | URL (typical) | Audience |
|---|---|---|
| Public website | https://www.sawtee.org / staging host | Visitors, researchers, partners |
| CMS / Admin | /admin | Staff who create and publish content |
This documentation explains:
- How editors use the CMS day to day
- How that content shows up on the frontend
- How local / staging / production environments fit together
It is not a full developer API reference. Engineering notes stay in the main README.
Mental model
Admin CMS → database + media library → Inertia pages → public React UIEditors never edit React files. They edit posts, publications, pages, menus, homepage sections, feature cards, and Site Settings (footer, search, SEO defaults, error copy, and similar strings) in /admin. The public site reads that data on each request (with short caching for home/menus/sitemap).
Where to go next
- New to the project → Local setup
- Editor handbook → CMS overview
- Public wording (footer, search, errors) → Site settings
- How the public site is structured → Website overview
- Staging vs production → Environments