1.5 KiB
Bundle 1 — mock content initialization
The owner approved the original source-content review, then directed that the frontend show mock content until staff enter content through Django admin. The existing migrations, including 0005_seed_current_website_copy.py, remain unchanged.
Use the backend management command seed_mock_content.py after migrations and before enabling CMS page rendering:
python manage.py seed_mock_content --dry-run
python manage.py seed_mock_content
It replaces content for records without a Django admin change-history entry with clearly labeled Persian sample copy, including About items. A record with an admin change entry is preserved as a whole. Re-running the command is safe; --dry-run reports intended work without writing. The command is explicit and is not run automatically by deployment or migration.
Images remain empty because no approved mock image files exist; the frontend treats them as optional. Contact mock URLs use example.invalid and the mock email uses that reserved domain.
The frontend flag remains off by default. The page routes still use legacy rendering until later Bundle 1 tasks wire them to the adapter. Do not enable CMS rendering in a target environment until T08's database audit is complete and the command's dry-run output is reviewed.