How madi6116/amore-cms works
This repository configures a Sanity Studio for Amore Weddings and defines three editable document types: services, owners, and site settings. Editors work in the Studio; its configured schema describes the content available for editing, and the README characterizes the Studio as connected to Sanity’s backend. The excerpts show schema registration and project configuration, but not runtime persistence or backend calls, so those links are documented at a high level only.
Main entry points: index.js Schema registry · sanity.config.js Studio config · service.js Service document · owner.js Owner document
Components 8
Studio configuration
- Studio config
sanity.config.js - Sanity Studio
Content models
- Schema registry
schemaTypes/index.js - Service document
schemaTypes/service.js - Owner document
schemaTypes/owner.js - Site settings
schemaTypes/sitesettings.js
Other components
- Content editor
- Sanity backend
Connections 7
- Content editor → Sanity Studio: edits content
README.md - Studio config → Sanity Studio: configures
sanity.config.js - Studio config → Schema registry: registers schema
sanity.config.js - Schema registry → Service document: includes
schemaTypes/index.js - Schema registry → Owner document: includes
schemaTypes/index.js - Schema registry → Site settings: includes
schemaTypes/index.js - Sanity Studio → Sanity backend: connects to
README.md