yavsc/doc/architecture
Paul Schneider 4ba1aa8858 doc: correct Yavsc.Blogs role (backend, not front)
When documenting the per-project layout in the previous commit,
I described Yavsc.Blogs as 'Sous-domaine front web specifique
au blog', which is wrong: Yavsc.Blogs contains only ApiController
classes, services and models — no Razor views. The plan is to
deploy it as a headless backend API on a dedicated subdomain in
production, while the blog front (Razor views) stays in
Yavsc.Org to share rendering and auth.

Correct the description, the ASCII diagram, the table row, and
the 'why' paragraph accordingly.
2026-06-27 15:05:24 +01:00
..
decoupage-organisation.md doc: correct Yavsc.Blogs role (backend, not front) 2026-06-27 15:05:24 +01:00
dictionnaires-metier.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
domaine-musical.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
domaines-activite.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
licences.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
offres-frontmatter.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
postit-oidc.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00
workflow-multi-parties.md doc: split Architecture.md into per-topic pages 2026-06-27 13:45:31 +01:00