Pre-release Checklist

This sample post is closer to a real team note. It simulates the kind of final verification record people keep before release. Compared with the feature walkthrough post, it is shorter and reads more like an actual delivery checklist.

Release Scope

• Replace homepage content with sample data
• Add the missing Categories entry to navigation
• Replace friends, about, and footer copy with neutral content
• Remove historical posts and keep only a compact demo set

Pre-release Checks

Content

• Titles, descriptions, and author info no longer expose personal details
• The total post count stays intentionally small so the demo site does not look noisy
• Tags and categories each keep enough coverage to show archive pages correctly

Functional

• Search can find keywords such as canary release, rollback, and on-call
• Code copy button works
• Math formulas and images render without layout issues
• Dark mode remains available while English is the default UI language

Rollback Plan

If the content structure looks wrong after release, handle it in this order:

1. Roll back the article directory and restore _posts first.
2. If navigation or site title is still broken, then restore _config.yml and _config.oranges.yml.
3. Check for stale cache and regenerate static files last.

hexo clean
hexo generate

Risks

Risk	Impact	Mitigation
Dependencies are missing	Local build cannot run	Install first, then generate again
Comment service is not configured	Comments do not render	Acceptable for a demo site
Demo external links are unavailable	Page structure is still valid	Replace with production links later

Conclusion

The purpose of this post is not to show formatting tricks. It is to make the site feel like a real team handoff record. For a template project, that usually looks more natural than a pure tutorial.