Record completed internal CMS rollout
This commit is contained in:
+15
-7
@@ -19,13 +19,21 @@ Phase 6 adds two validated Markdown collections:
|
||||
homepage.
|
||||
|
||||
Both collections require frontmatter and support `draft: true`. Draft entries
|
||||
are excluded from the rendered pages and sitemap. This is a Git-backed pilot;
|
||||
it does not add a CMS or client-editing access.
|
||||
are excluded from the rendered pages and sitemap. The internal Decap CMS now
|
||||
edits these collections through the protected `cms` staging branch; client and
|
||||
public editing remain disabled.
|
||||
|
||||
Images must live under `public/images/`, be referenced with descriptive alt
|
||||
text where rendered, and remain at or below the 500 KiB pilot limit. The build
|
||||
will reject malformed site JSON and oversize source images.
|
||||
Journal `pubDate` and optional `updatedDate` fields use Decap's supported
|
||||
`datetime` control in date-only UTC mode. New posts default `pubDate` to the
|
||||
current UTC date. Repository verification rejects the unsupported `date`
|
||||
widget so the missing-control failure cannot silently return.
|
||||
|
||||
CMS images must live in the flat `public/images/uploads/` directory and be
|
||||
referenced with descriptive alt text where rendered. Approved source rasters
|
||||
may be at most 25 MiB; each build produces a metadata-free public copy no
|
||||
larger than 1920 pixels or 500 KiB. The build rejects malformed site JSON,
|
||||
disallowed image signatures, nested upload paths, and oversized sources.
|
||||
|
||||
Each selected build also generates `sitemap.xml` and `robots.txt`. Preview
|
||||
builds disallow indexing; a future approved production build must set
|
||||
`DEPLOY_ENV=production` to publish crawlable robots rules and the sitemap URL.
|
||||
builds disallow indexing; production workflows set `DEPLOY_ENV=production` to
|
||||
publish crawlable robots rules and the sitemap URL.
|
||||
|
||||
Reference in New Issue
Block a user