CivicPress 0.7.1 is out. No breaking changes, no PHP bumps, nothing to migrate. What this release does is get the theme ready for WordPress 7.0 and finish off a few arcs we started in the 0.6.x line.
WordPress 7.0 navigation and block supports
WordPress 7.0 is around the corner and brings meaningful changes to the Navigation block plus new block supports across core. We’ve shipped improvements to the Navigation block this release and added support for the new 7.0 block features so editors and developers won’t have to wait once the WP 7.0 update lands.
This is the kind of work that doesn’t show up in a feature demo. Staying current with WordPress core is unglamorous (we said this in the 0.7.0 PHP 8.2 post and it still applies), and it’s also what keeps CivicPress viable as a long-term foundation for a government site rather than a year-one bet.
Super Editors can now edit the Privacy Policy
In 0.6.9 we shipped the Super Editor role to give content teams more authority without handing out full Administrator access. One thing Super Editors couldn’t touch was the Privacy Policy page content, which is a real-world gap: privacy policies need updates, and routing every update through an Administrator is the kind of small friction that adds up.
That gap is closed in 0.7.1. Super Editors can now edit the Privacy Policy page content directly.
White-labeling now extends to the login screen
The white-label work we started in 0.6.8 covered the CivicPress Admin Menu (child-theme-controlled menu name, filterable icon, custom title page). 0.7.1 extends that same treatment to the WordPress login screen. Agencies running CivicPress now get a login experience that matches the rest of their branded admin, not a generic wp-login.php page with the WordPress logo on it.
Small thing. Real impact for anyone who’s ever screen-shared the login page for a content team training.
Everything else
The rest of 0.7.1 is the usual polish and dev work:
- USWDS Vivid Colors removed for better brand color support
- External links now get automatic
relattributes and new-tab behaviors - Fixed: disabling comments was interfering with the Notes feature
- Dev: unused User/Author content and endpoints disabled (reducing surface area we don’t use)
- Dev: template parts can now be hidden from the parent theme
- npm dependency updates
The full list is in the changelog if you want every line item.
Ready to update? As always, test in a staging environment before deploying to production.
The complete changelog lives at civicpress.us/changelog.
Have questions or want to see CivicPress in action? Get in touch.