Docs → CORA Admin
Core Features
CORA Admin
An overview of the customized WordPress admin experience CORA provides.
On this page
What’s different
Out of the box, CORA customizes the WordPress admin to reduce noise for non-developer users. The goal is a cleaner backend that surfaces the tools editors actually need without exposing settings that could cause problems.
CORA Admin v1 is an intentional MVP. The full Editor vs. Super Admin split is on the roadmap — currently all authenticated users see the same customized view.
Navigation & layout
The CORA admin modifies the default WordPress sidebar to:
- Surface CORA-specific settings under a dedicated CORA menu section
- Group plugin settings under logical categories rather than scattering them across the sidebar
- Reduce visual clutter by hiding developer-only items from the default editor view
- Add an Other Content section for global site options
Other Content (Global Options)
Other Content is CORA’s global options page — accessible from the admin sidebar. It contains tabbed settings contributed by the theme, child theme, and installed plugins.
Common tabs:
- Google Tag Manager — add GTM container ID and GA4 Measurement ID
- Alert Bar — configure and activate the site-wide announcement bar
- Theme Options — global settings specific to the child theme
Developers can register new tabs to Other Content using WordPress options or ACF’s options page API. See the CORA Theme Options plugin for reference.
User roles
- Administrator — full access to all CORA and WordPress settings
- Editor — content creation and publishing, no plugin or theme settings access
- Author — create and publish their own posts only
The User Role Editor plugin (included in the default stack) allows fine-grained capability adjustments per role.
Current limitations
Known gaps in v1 that are on the roadmap:
- No distinct Editor vs. Super Admin view — all roles see the same admin interface
- CORA feature plugin settings are not yet unified under a single CORA dashboard
- Gravity Forms reporting is still in the core admin — will be extracted to its own plugin in a future release
