YENRA — CMS DECISION AND RESTORE WORKSHEET
Companion: https://yenra.com/linux-content-management-system/

Publication / decision owner / date:
Editors and reviewers / technical comfort / required roles:
Representative draft-to-correction task:
Required content types / preview / approval / scheduling / languages:
Stable URL and redirect requirements:
Search / forms / identity / other integrations and owners:

Candidate / architecture / supported component versions:
Where editing, rendering, storage and dynamic functions run:
Acceptance evidence (expected, actual, owner):
- Draft, headings, image alternatives, captions and links:
- Private preview and role restrictions:
- Review, publish, correct, recover an earlier revision:
- Search, forms, redirects and scheduled publication:
Extensions and why each is required:
Runtime, database, OS and extension update owners:
Writable directories / code ownership / credential storage:
Staging controls for email, payments and copied private data:
Rollback compatibility between code and database:

Backup inventory:
- Database or content source:
- Original media:
- Configuration and custom code:
- Themes/plugins and dependency records:
- Required credentials and external service data:
Consistency procedure / backup interval / off-host copy / access controls:
Recovery point objective (acceptable data loss):
Recovery time objective (usable service restored):

Restore rehearsal — isolated target and date:
Backup obtained at / restore started at / usable site verified at:
Actual end-to-end recovery interval:
Old/new articles, media, editor login and correction tests:
For static publishing: rebuild from recorded source and tool versions:
Missing items / measured gaps / owner / next rehearsal:
Selection rationale and unresolved requirements: