- Article
- Beginner
- 5 minutes read
- Reviewed August 3, 2026
A WordPress installation normally provides two main interfaces: the administration area used to manage the website and the public frontend presented to visitors.
They use the same underlying content, users, themes, plugins and database, but they serve different purposes.
The Public Website
The public website is the frontend people visit through the main domain.
It is generated according to:
- The requested URL.
- Published content.
- The active theme.
- Templates and styles.
- Active plugins.
- User login state and permissions.
- Cache and server configuration.
Public does not mean that every page is available to everyone. WordPress can display private, password-protected, restricted or account-specific content when configured appropriately.
The WordPress Administration Area
The administration area is the interface used to manage WordPress.
Its default location is commonly:
https://example.com/wp-admin/
Unauthenticated visitors are normally redirected to the login screen.
After login, WordPress shows screens according to the user’s capabilities. An Editor and an Administrator should not necessarily see the same controls.
The Dashboard Home Screen
The Dashboard is the administration home screen.
It can display widgets such as:
- At a Glance.
- Activity.
- Quick Draft.
- Site Health information.
- WordPress events and news.
- Plugin-specific summaries.
The available widgets can change by WordPress version, user permissions and active plugins.
The dashboard is a starting point, not a complete report of website health.
The Administration Menu
The main administration menu provides access to areas such as:
- Posts.
- Media.
- Pages.
- Comments.
- Appearance.
- Plugins.
- Users.
- Tools.
- Settings.
Plugins and custom content types can add their own menu items.
Menu visibility is controlled partly by capabilities. Hiding a menu item visually is not a substitute for enforcing permission checks.
Administration Screens
Each administration screen generally includes:
- The toolbar and header area.
- Main navigation.
- Page title and actions.
- Work area.
- Contextual help.
- Screen Options where available.
- Notices.
- Footer.
List screens commonly include filters, bulk actions, search and sortable columns.
Editing screens vary according to content type, editor configuration and plugins.
Screen Options and Help
The Screen Options panel can control visible columns, page size, editor panels and other screen-specific preferences.
Contextual Help provides information relevant to the current administration screen.
These controls are easy to miss but useful when an expected panel or column is not visible.
The Toolbar
The toolbar appears at the top of administration screens and can appear on the frontend for logged-in users.
It provides shortcuts for actions such as:
- Visiting the website.
- Creating content.
- Opening comments or updates.
- Editing the current page.
- Accessing account options.
Themes and plugins can add toolbar items.
The Content Editor
WordPress uses a block-based editor for posts, pages and other supported content types.
The editor can include:
- Block inserter.
- Content canvas.
- Document settings.
- Block settings.
- List View.
- Publishing controls.
- Revisions and status information.
- Plugin panels.
A content type may use the block editor, a classic interface, a custom application or a combination of panels.
The Site Editor
The Site Editor is available when a compatible block theme is active.
It can be used to manage areas such as:
- Templates.
- Template parts.
- Styles.
- Navigation.
- Patterns.
- Site-wide design.
It should not be confused with the editor used for the content of an individual post or page, although both use blocks.
Classic themes may use the Customizer, widget screens, menus and theme-specific settings instead.
How Administration Changes Reach the Frontend
When you publish or update content, WordPress stores changes in the database.
The frontend retrieves that content when a visitor requests the relevant URL.
A change may not appear immediately because of:
- Page cache.
- CDN cache.
- Browser cache.
- Scheduled publication.
- Draft or pending status.
- Incorrect template.
- Permission restrictions.
- Editing a different environment.
Understanding the publication state and cache layers helps diagnose “I changed it, but nothing happened” problems.
Preview Is Not the Same as Published Output
Preview allows an authorized user to inspect unpublished or updated content before publication.
A preview can differ from the final visitor experience because:
- The user is logged in.
- Caching is bypassed.
- Personalized content changes.
- External integrations behave differently.
- Responsive or browser conditions differ.
After publishing, verify the page as a logged-out visitor and on relevant devices.
User Permissions Shape the Interface
WordPress roles contain capabilities.
A user may be able to edit posts without installing plugins or changing settings.
This protects the website and keeps interfaces simpler.
Use the least privilege necessary. Do not share a single administrator account across a team.
The Frontend Can Be Separate
In a headless WordPress architecture, the public frontend may be a separate application.
WordPress still provides administration, content and APIs, while another system renders the visitor interface.
The distinction between administration and frontend becomes even clearer in this architecture.
Common Dashboard Problems
A Menu Item Is Missing
The user may lack the required capability, a plugin may be inactive or the interface may have been customized.
A Panel Is Missing from the Editor
Check editor preferences, Screen Options, content type support and plugin configuration.
The Frontend Does Not Match the Editor
The theme, template, custom CSS, block styles or cache may affect presentation.
The Website Looks Different While Logged In
Administration toolbar space, personalized content, cache bypass or permission-based output can change the page.
Frequently Asked Questions
Is the dashboard visible to website visitors?
Not normally. Users must authenticate, and the available administration screens depend on permissions.
Can I customize the administration area?
Yes. Plugins and custom development can add, remove or reorganize screens, notices and fields. Changes should preserve accessibility and permissions.
Why can an Editor not install plugins?
Installing plugins is a high-privilege action reserved for users with the relevant capability, normally Administrators in a single-site installation.
Is the Site Editor available on every WordPress website?
No. It depends on the active theme and WordPress configuration. A compatible block theme is required for the complete Site Editor experience.
Continue Learning
Previous: How to Install WordPress