Publish, recover and maintain

LESSON 8.1

Prepare a launch you can reverse

Your goal: Use a launch checklist and a realistic migration method.

A finished practice site is not automatically a live website. A real launch needs hosting, a domain, HTTPS and a migration method that transfers the database and files and handles URL changes. Follow your host’s supported migration process and test a staging copy first. Do not assume a Playground ZIP can simply be uploaded as a WordPress plugin.

See it in practice

Before launch, back up both source and destination. Confirm who owns the domain and who will maintain the site. Review page titles, menus, images, redirects and contact information. Remove demo wording only when the information is real and ready. Enable public indexing only when the site should be discoverable.

Try a small change

Prepare a launch checklist for Northside. You can complete this course without buying hosting or publishing: mark launch as a rehearsal and retain the demo notice.

What should happen, and why?

A rehearsal is a valid learning outcome. A public launch introduces real operational responsibilities; it should be deliberate.

I read this lesson and tried the small change.

LESSON 8.2

Prove recovery and plan maintenance

Your goal: Test a restore and define a sustainable care routine.

A backup is only useful when you can restore it. Keep database and files together and store a copy away from the running site. On a separate practice installation, import your saved Playground ZIP or follow the host’s restoration instructions. Check the restored pages, menu and images before trusting the recovery process.

See it in practice

Plan a recurring review of backups, updates, critical links and contact delivery if a real form is added. Use staging for risky changes and keep a short change log. Collect only information the website actually needs. Do not upload private backup archives into a public Media Library.

Try a small change

Restore a copy into a separate workspace and follow Home → Services → Contact. Record the backup date and what worked. Write a handover note with ownership, maintenance tasks and a recovery location, without passwords.

What should happen, and why?

The handover makes the website maintainable by a future you or another responsible person. A completion checkmark is your record of this test, not an automated inspection of the remote site.

I read this lesson and tried the small change.

GUIDED BUILD

Put the lesson to work.

Finish the three-page project and run the final checklist below.
Export a full recovery copy and restore it in a separate workspace.
Write a short handover and decide whether this is a launch rehearsal or an actual hosting project.

Check your work

My three-page site passes the final review checklist. I restored a separate copy and checked pages, navigation and images. I wrote a maintenance and ownership handover without secrets.

These are your own practice confirmations. We do not inspect your external WordPress site.

BREAK / FIX

Find the cause. Check the repair.

You exported a theme, but the fresh installation has no Services page or uploaded workshop photo.

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

Check what kind of export you created.

Hint 2 — The principle

Theme templates/styles and the complete site are different packages.

Hint 3 — Explained repair

Restore a full site backup containing the database and uploads. A theme export does not include all pages and media. Recheck the restored content, then create a correct full backup.

I tested the repair or wrote a reasoned recovery plan.

Prepare a launch you can reverse

See it in practice

Try a small change

Prove recovery and plan maintenance

See it in practice

Try a small change

Put the lesson to work.

Check your work

Find the cause. Check the repair.

Five questions. As many tries as you need.

Keep these references