MODULE 6 OF 8 · 60–90 minutes
Add features without losing control
Loading progress…
LESSON 6.1
Decide whether you need a plugin
Your goal: Evaluate a feature before installing extra software.
A plugin adds behavior such as forms, backups or search features. A theme supplies the presentation. Start with a clear requirement and check whether WordPress already meets it. Installing several plugins for the same job can create conflicting settings and more maintenance.
See it in practice
For Northside, a contact-information page with a demonstration email link is enough for this course. A real form adds delivery, spam handling and personal-data responsibilities. If you later choose a form plugin, use an official source, inspect maintenance and compatibility, back up, then test on staging. No paid plugin is required here.
Try a small change
Write a short decision: “We need visitors to find contact details; core blocks meet that need.” Then identify one future feature that might justify a plugin.
What should happen, and why?
You are choosing software to satisfy an actual task. The number of installed plugins is not a measure of a complete website.
LESSON 6.2
Roles and a safe change process
Your goal: Give collaborators appropriate access and isolate failures.
An Administrator can change important site settings and software. An Editor manages content, while a Subscriber has much less access. Match permissions to the job instead of making everyone an administrator. Your course account remains a learner account; your practice installation has a separate administrator.
See it in practice
Before a plugin or theme update, take a full backup and test the change on staging. Check the pages and functions the component affects. If something breaks, identify the last change and use a tested restore or rollback method. Randomly changing several components makes the cause harder to find.
Try a small change
In your practice dashboard, inspect the Users screen and current role. Make a change log entry for your next theme or plugin update: what changed, backup location and which pages you will check.
What should happen, and why?
A change log turns “it stopped working” into a sequence you can investigate. Do not share administrator passwords as a collaboration method.
GUIDED BUILD
Put the lesson to work.
- Create a plugin decision note for the Contact page; use core blocks for the course demo.
- Review roles in your separate practice site and record the minimum role for a content editor.
- Write a backup → update → test → restore plan for one component.
Check your work
These are your own practice confirmations. We do not inspect your external WordPress site.
BREAK / FIX
Find the cause. Check the repair.
After two similar layout plugins were activated together, the page spacing changed unexpectedly.
Reproduce this only on a disposable practice copy if it is safe. Otherwise explain the diagnosis and recovery steps in your notes.
Hint 1 — Where to look
Compare the time of the visual change with the change log.
Hint 2 — The principle
Two components can both apply styles to the same blocks.
Hint 3 — Explained repair
On the practice or staging copy, deactivate one newly added component at a time and recheck the same page. Keep the smallest set that meets the requirement; restore the known-good backup if necessary.
CHECK YOUR UNDERSTANDING
Five questions. As many tries as you need.
Get at least four correct. After checking, read the explanations and try again. All six practice checks and a passing quiz complete this module.
Keep these references
Official documentation. Screen labels can differ by theme and WordPress version.