Preferred low-complexity replacement
Keep the existing posts and asides category. Create a notes page, add a Query Loop block filtered to that category, choose a compact template and link the page from navigation. This removes the retired display dependency while preserving WordPress-native content.
Choose the implementation
| Approach | Content model | Best for | Main tradeoff |
|---|---|---|---|
| Category + Query Loop block | Core blocks and taxonomy | Block themes with no custom PHP requirement | Layout control varies by theme and site-editor experience |
| Posts + dedicated category | Standard WordPress posts | Short updates that should remain in feeds and archives | Requires theme rules to keep short posts visually distinct |
| Custom post type | Separate structured content type | Updates needing their own fields, archive and permissions | Requires durable registration and a migration plan |
| Curated notes page | One maintained page or collection | Low-volume notes where simplicity matters most | Individual notes may lack stable URLs and feed entries |
Migration checklist
- Identify the exact category selected by Sideblog.
- Export or back up every post, term and media reference.
- Record the current archive and individual URL behavior.
- Build the new display in staging.
- Verify ordering, excerpts, dates, feeds and mobile layout.
- Deactivate Sideblog and retest before deleting its files.
- Add one-hop redirects only for URLs that genuinely changed.
When a custom post type is justified
Use a custom type when notes require different permissions, fields, editorial states or API behavior. Register it in a durable site plugin rather than a theme, and document how content will be exported if that implementation is later retired.
Frequently asked questions
What is the easiest Sideblog replacement?
For most sites, retain the asides category and display it with a Query Loop block or maintained theme template. This changes presentation without moving the posts.