Website training that puts your team in control.
A website handover should leave people ready to use the site. WebXd plans website management training around the updates your team owns, with guided practice and instructions they can use again. Turn a familiar request into a task someone can finish with confidence.
Build the lesson around the person doing the update.
Start with a short list of recurring requests. A communications editor might update an event, while a department reviewer checks the details and a publisher approves the release. That division tells us what each person needs to learn and which decisions belong to someone else.
CMS training should use the access people will have after the session. Review the actual permissions before choosing the exercises, including custom roles and approval rules. Someone who edits a biography may need a focused lesson on that template, rather than a tour of every administration screen.
| Responsibility | Lessons | Repeat-task check |
|---|---|---|
| Content editor | Find the right page. Update text and media. Save a draft. | Prepare an accurate update in the assigned template. |
| Reviewer or publisher | Check the preview. Return corrections. Approve the release. | Explain what is ready, what needs revision, and who can publish. |
| Website owner | Recognize access limits. Keep guides current. Route technical issues. | Identify the right person when a task exceeds an editor's access. |
Give practice its own place.
A learner needs room to try an edit, notice a mistake, and try again. Agree on a staging site or another approved practice area before the lesson. Use representative content that can be changed safely, and make the environment clearly distinguishable from the public website.
Check what a practice action can trigger. A copied form might still send email, and a connected workflow could reach a live system. Test those boundaries with the website owner and agree which actions to isolate. Preparation or configuration work belongs in the scope when the practice area needs it.
- A visible practice-site label and separate sign-in route
- Learner accounts with the intended permissions
- Sample pages, images, and files approved for practice
- An agreed reset method and owner for blocked tasks
Rehearse the update people will actually see.
Consider an event page whose date has changed. The exercise asks an editor to find the page, change the date, replace the event image, and prepare it for review. The instructor watches the work and explains unfamiliar controls as they appear. Practice stays connected to a request the learner recognizes.
The review includes the public result, not just the editing screen. Check the date wherever the template displays it, follow the registration link, and inspect the page on a narrow screen. A reviewer can then return a specific correction, giving both people practice with the approval path.
Recovery is part of the exercise. Introduce a deliberate content mistake, compare the saved versions where revisions are available, and rehearse the approved way to restore the intended text. Revisions may not restore a replaced file or a wider site change. The guide should identify when to stop and ask the site owner.
A new date. The same publishing standards.
- PrepareFind the event in the practice site and confirm the approved date.
- EditUpdate the date and image. Check alternative text and the registration link.
- ReviewSave a draft, inspect the preview, and send it through the agreed approval route.
- RecoverCorrect a deliberate text mistake using the available revision controls.
Keep a guide beside the next edit.
Useful documentation starts with the task name someone will search for later. A guide to replacing an event image should show the correct template and the checks that follow the upload. Keep the screenshots tied to the site's current interface, with enough explanation to help a new colleague follow the same path.
Each guide needs a clear starting point, the required access, and a way to recognize a finished task. Add the common stumbling points found during practice and a contact for questions outside the lesson. Agree who will revise the guide when a template or publishing rule changes.
- Task title and the page or template it applies to
- Required access and approved practice material
- Steps with screenshots of the actual editing interface
- Preview, approval, and recovery checks
- Document owner and last review date
Make the final check a real task.
Watching an instructor demonstrate a change is different from making it yourself. Agree on a practical check for each lesson, then ask the learner to repeat a comparable task using the guide. Observe where they can continue independently and where another example or a clearer instruction would help.
For the event exercise, the check might be a complete draft with the correct date, a working link, and the right review status. Record what was attempted and any follow-up practice needed. This is a check of an agreed website task, not a claim of formal certification.
People may need different ways to follow the lesson. Discuss pacing and accessible materials before scheduling, along with whether small groups or individual practice suit the team. An unresolved access problem should be recorded separately from a learner's understanding so the next action goes to the right owner.
- Can find the correct content
- Can make and preview the edit
- Can follow the approval route
- Knows the recovery limit
Agree what training needs to cover.
Bring the website address, its platform, and examples of updates the team expects to handle. Note who edits, who approves, and where people currently get stuck. Those details help define the lessons and any preparation needed, including practice access, documentation, and the check at the end.
Training develops the team's ability to do agreed work. Ongoing CMS support helps with questions and changes as they arise, while website maintenance covers separately scoped technical care. Choose the help the team needs alongside the lessons, and keep those responsibilities clear in the proposal.
Can you train our team on an existing website?
An existing site can be the starting point after a review of its platform, templates, and access. Share the custom features people use and the updates they want to make. The proposed lessons should reflect the configured site, including any limits that need development work before a task becomes editable.
Does this include WordPress or Drupal training?
WordPress and Drupal lessons can focus on the editing tasks available in your installation. Plugins, custom templates, and permissions affect the screens people see. Confirm the platform and its configuration during scoping so the exercises and guides match the site the team will actually use.
What determines the training cost and schedule?
The proposal depends on the task list, learner roles, session format, and preparation required. A focused lesson for one template has a different scope from several publishing roles and custom workflows. Agree on documentation, practice setup, and follow-up checks before setting the budget and schedule.
Can we keep materials for new staff?
Include reusable task guides in the agreed deliverables and discuss recordings if they would help the team. Confirm consent, storage, access, and any sensitive material before recording a session. A guide owner should review the materials when the website changes so a new colleague starts with current instructions.