Architecture Audit
dgosocial
Reuse
- Disciple-making content vocabulary: Discovery Bible Studies, trainings, lessons, reading plans, memory plans, stories, videos.
- Pest feature-test style around user-visible behavior.
- Planning Center as an OAuth/integration concept for later authenticated workflows.
Rewrite
- Tenant model. Jetstream teams are not the right foundation for Platform's Organization -> Site -> Domain hierarchy.
- Public routing. Platform should resolve the current site by domain from the beginning.
- Admin structure. Use Filament resources for administration instead of custom dashboard screens until a custom interface is justified.
- Content ownership. Future content models should explicitly belong to Organization or Site.
Defer
- Planning Center integration until a concrete workflow needs it.
- Bible XML and spreadsheet imports until resources/training slices require them.
- Social login and mobile/API authentication until the public multi-site foundation is stable.
Discard
- Copying Laravel 9 Jetstream/Socialstream scaffolding into the new app.
- Treating personal teams as tenant boundaries.
- Broad upfront service/repository/action layers without a repeated maintenance problem.
Initial Platform Direction
Start with a small Laravel-native vertical slice:
- Organizations own Sites.
- Sites own Domains.
- The web request resolves the current Site from the incoming host.
- Public rendering uses the resolved Site and does not leak another Site's content.
This keeps the first milestone focused on proving multiple branded websites from one Laravel application.
The seed data includes these staging domains for Forge/DigitalOcean deployment testing:
platform.3r.mediathechapeltyler.3r.mediadisciplego.3r.mediathechapelcc.3r.media
For local development, the seed data also includes platform-chapel-tyler.test and platform-disciplego.test to avoid colliding with existing Herd sites.