Using WordPress admin: dividing content, design and administrator duties

When taking over WordPress admin, you do not need to learn every button on the first day. Identify three daily tasks, such as updating announcements, correcting contact details and checking comments, and learn the relevant menus through those tasks. Separating content work from site-wide settings helps avoid changing the whole website just to revise a short passage.

Consider two people maintaining a club website together: one prepares event posts, and the other checks and publishes them. The workflow is based on official WordPress documentation, and the role descriptions assume a default single-site installation. Plugins, custom permissions and a Multisite network can change actual capabilities, so verify them against the site's current settings.

Confirm the website and account first

After signing in, check the URL, site name and current account. Similar-looking production and test sites are easy to confuse when you are busy; give the test site a clear label and use separate bookmarks. Even when entering WordPress through a hosting platform, confirm that you selected the correct website before making changes.

The administration area usually has a top toolbar, a navigation menu and a main workspace. The Dashboard shows content activity and site information, but some messages come from plugins or vendors. Before acting on promotions, installation prompts or warnings, identify their source and whether they are needed. Not every notice is an urgent requirement from WordPress core.

If a feature is missing, check your role, theme and plugins first. Some screens have adjustable display options, and block themes and classic themes may use different appearance controls. When sending a screenshot to the administrator, explain the task you need to perform. That makes it easier to find an appropriate solution than simply asking for every permission.

Find content controls by task

Posts suit content published over time, such as club event news. Pages suit more stable site information, such as how to join and contact details. The Media Library manages uploaded files, while Comments handles reader responses. Learn these four areas first, then explore categories, excerpts and other settings.

Before each edit, locate the right item by title, status or date, then open the editor. If titles are similar, check the URL and content before changing anything. Bulk editing saves time, but applying it to everything is unsuitable when you are new to the site. First check its effect on an item that will not disrupt operations, so you understand the scope.

When the club changes an event venue, correct the event page first, then check whether related announcements also need updating. Renaming an image in the Media Library does not change text inside the image. Nor should you update only the homepage excerpt while leaving old details on the full page. List every location that needs updating to avoid conflicting information.

Distinguish individual content from site-wide design

Body blocks in the post editor mainly affect that post. With a block theme, the Site Editor can manage templates, styles and shared structures. Changes to a header, footer or shared style may affect many pages. Before editing, identify whether you have selected post content, a template or a shared component, and review the change list when saving.

A site with a classic theme may use Customize, Widgets or the theme's own settings to change its appearance. A missing Site Editor does not mean the installation is broken; check the theme type first. If a page-builder plugin is installed, learn which pages it controls so mixing editing methods does not damage existing layouts.

For people who are not responsible for design, a useful initial agreement is to edit only content and images, leaving fonts, site-wide colors, navigation and templates to designated staff. This is a suggestion for dividing work, not a rule that content editors can never adjust design. When needs change, agree on specific permissions and acceptance checks.

Assign roles by responsibility, not seniority

Among the default roles, an Administrator manages a single site; an Editor can manage and publish posts, including those by other authors; an Author primarily manages and publishes their own posts; and a Contributor can prepare their own posts but cannot publish them. A Subscriber mainly manages their profile. This is an overview of default capabilities; plugins or administrators may alter them on an actual site.

If the club requires every announcement to be reviewed, do not automatically assign the Author role just because a colleague writes content: Authors can publish their own posts by default. First list the required capabilities, including uploading media, editing others' content, publishing and deleting. Then choose an appropriate role or reviewed permission configuration.

Give everyone their own account to support suspension, handover and accountability. If someone temporarily helps configure a plugin, agree to review whether they still need those permissions once the work is finished. Before deleting a user, resolve ownership of their content so you do not accidentally delete both a departing person's account and their posts. Keep a backup and obtain administrator confirmation when needed.

Use a consistent process for each change

Record what you intend to change, its original value and the expected result, then make a limited change. Save and preview content as a draft first where appropriate; remember that updates to already-public posts affect visitors. If a page has forms, buttons or external links, test the associated workflow as well as its layout, confirming the destination and how data are received.

Before changing plugins, themes or site-wide settings, confirm the backup and recovery method, and test on a staging site where appropriate. Avoid changing several dependent components at once, which makes faults hard to trace. Recording the time and items changed also helps other administrators avoid working on the same area simultaneously.

1. Confirm the site, account, content URL and purpose; retain the original values or necessary backup.
2. Make the smallest relevant change and check whether it affects one item or the whole site.
3. Preview desktop and mobile layouts, and test links, forms and the signed-out state.
4. Submit for review or publish according to your permissions, record the result and notify the person taking over.

Read Site Health and report problems

Site Health under Tools provides status checks and environment information to help you understand versions, plugins and settings. Its Info screen displays information; it is not a place to change every server setting. For recommended improvements, first understand the impact and who is responsible. Having no warnings does not replace testing forms, sign-in and content functionality.

When reporting a problem, include the URL, time, steps taken, error message and affected scope, with passwords and personal information redacted. If it started just after an update, include the updated items and backup location. This record gives the next person known facts to work from instead of making them guess which buttons you pressed.

Read the full description

Original diagram dividing WordPress work into content updates, site-wide design and account administration.

Building your first WordPress site

Planning website maintenance

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress