Record approved direct content API checkpoint

This commit is contained in:
2026-09-27 11:40:16 +03:30
parent b6e0d41691
commit 01edaa0d8a
2 changed files with 3 additions and 3 deletions

View File

@@ -27,7 +27,7 @@ Create one fixed record per page and one shared site record, using explicit text
### 3. Serve current content
Expose only the small public read API needed by the frontend for shared site content and the four fixed pages. Responses contain current text, media URLs/alt text, and SEO fields. Remove revision IDs, status, draft preview, publish, and restore from the schema. Define empty-record behavior and cache handling so a successful admin save appears on the next public request.
Expose only the small public read API needed by the frontend for shared site content and the four fixed pages. The implementation and response shapes are documented in the backend [content API v1 note](../../guilan-ace-backend/docs/content-api-v1.md). Responses contain current text, media URLs/alt text, and SEO fields. Remove revision IDs, status, draft preview, publish, and restore from the schema. Define empty-record behavior and cache handling so a successful admin save appears on the next public request.
**Check:** anonymous reads return current saved values; unknown pages and missing records have explicit responses; an admin save is visible through the API immediately. No draft or preview route exists.