GuilanCE/guilan-ace-deployment
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record mock content initialization workflow

Browse Source
This commit is contained in:
Amirhossein Khalili
2026-09-27 12:26:33 +03:30
parent 01edaa0d8a
commit 9954fbcc0d
3 changed files with 26 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tasks/bundle1-simplification-plan.md
View File

@@ -33,9 +33,9 @@ Expose only the small public read API needed by the frontend for shared site con
### 4. Populate reviewed starting content
Use the existing content inventory to prepare the four fixed records and site identity. Review disputed claims, contacts, and media rights before they become public. Import approved values once without overwriting subsequent admin edits. A small repeatable initialization/data migration is preferable to a general-purpose seed workflow; a dry run is only needed if the environment audit reveals existing data that could be overwritten.
Leave all existing migrations unchanged. Use an explicit `seed_mock_content` management command after migrations to ensure the five fixed records contain obvious mock copy until staff save content through Django admin. It replaces untouched migration-provided copy, preserves records with a Django admin change-history entry, supports `--dry-run`, and is never run automatically. Complete the T08 database audit before running it against a target environment; inspect the dry-run output first.
**Check:** compare each imported value and image with its approved source; a second initialization leaves edited records unchanged.
**Check:** confirm the command fills mock copy, skips admin-edited records, and is idempotent. Optional media remains empty. The owner reviews the mock output before frontend cutover.
### 5. Connect the frontend and verify SEO