Separates package creation from live deployment and requires staging, backup, rollback, and environment-specific checks before production changes.
Package is not deployment
A valid ZIP only proves archive structure and static checks. Production deployment still requires staging, backup, host compatibility, database and plugin review, cache behavior, browser tests, accessibility tests, and rollback.
Rollback
Retain the previous theme and plugin archives, database backup, applied content version, and configuration export before changing production.
Scope
This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.
Engineering considerations
- Identify the source, version, target environment, and owner.
- Separate observed values from estimates and externally reported values.
- Record trade-offs, unsupported cases, and fallback behavior.
- Link performance statements to a compatible benchmark methodology.
Verification questions
- What exact artifact, revision, backend, and environment were reviewed?
- Which assumptions could change the result?
- Which data should be retained so another engineer can reproduce the conclusion?