Build Your First WordPress Website with Codex in 24 Working Hours

Learn / Website development

16 steps · Four-page WordPress website

Build Your First WordPress Website with Codex in 24 Working Hours

By Henok Ahmed · Version 1.0.0 · 28 October 2026

Download runbook + prompt deck (ZIP) Open the prompt deck →

A step by step runbook with copy and paste prompts checks and troubleshooting

By Henok Ahmed

Version 1.0.0
Document HA-WEB-002 · Published 28 October 2026
Status: Published with author approval.
License: CC BY 4.0 for the educational text, prompts, tables and checklists; exclusions below.

Companion foundation guide: Building a Professional WordPress Website with Codex, Version 1.0.0, explains business, technical foundations, and delivery responsibilities. This runbook takes you from an open computer to a completed, tested four-page WordPress site.

What the time in the title means

Twenty-four working hours is a planning allowance, not a measured result, delivery promise, or fixed deadline. It covers a small, one-language informational/marketing site using an existing supported WordPress installation and a restrained design. The exercises have not been timed with a learner cohort.

Budget more time if you are learning the tools, replacing a damaged site, translating content, diagnosing hosting problems, or waiting for other people. Account creation, purchases, domain/DNS propagation, client waiting time, and interruptions are outside the estimate. Stop the clock for external waiting; do not skip checks to meet the title.

The four pages are Home, About, Services, and Contact. There is no payment, account system, booking engine, blog, or confidential upload. A phone/email contact route is the baseline. A contact form is an addition only when its configuration and delivery can be verified within the actual scope.

Two completion modes

Choose one in Step 3:

  • Practice: complete a fictional website on an access-appropriate test installation, verify the four pages and contact destinations, and produce handover/recovery records. No fictional business is presented as real to the public.
  • Client: complete an authorized real website, obtain owner acceptance, deploy to the approved destination, verify the public result, and hand over.

The same steps apply. Final status must distinguish these modes. An unapproved candidate is not a completed client delivery. Missing authorization or broken contact behavior is a blocker, even when the planned hours are exhausted.

Before the clock starts

You need:

  1. A computer, browser, working project folder, and current access to Codex.
  2. An available WordPress installation where you are authorized to work, its correct URL, and an authorized account. Use a test environment first. If you have none, arrange a supported local/hosted installation before this timed exercise.
  3. For a client launch, available hosting/domain ownership, HTTPS configuration, a production operator, and an owner able to approve the content and launch.
  4. Approved or fictional source information, authorized contact values, and rights to any images.
  5. A way to back up and restore the relevant environment, with hosting support available where needed.

Never paste passwords, recovery codes, or secret tokens into the prompts or project files. Sign in through the intended service yourself. Tool permissions still apply; these prompts do not override them.

A hosted Codex session requires the relevant connection. Offline content preparation is useful during an outage, but do not assume Codex will operate offline.

The work plan

Step Work Planned hours
1 Open the computer and prepare the workspace 0.5
2 Set the project working agreement 0.5
3 Complete the project brief 1
4 Verify WordPress and recovery arrangements 1.5
5 Prepare approved content 1.5
6 Fix the pages and editing approach 1
7 Define and review the visual direction 2
8 Build and save Home 3
9 Complete About Services and Contact 2
10 Verify contact and media 1.5
11 Correct mobile and keyboard behavior 2
12 Run acceptance checks and corrections 2
13 Record source and candidate 1.5
14 Obtain owner acceptance 1
15 Apply the approved deployment 1
16 Verify hand over and close 2
Total Active working allowance 24

You can divide this into several sessions. Complete a step's check before proceeding; the order is more important than the calendar.

How to use the prompts

The main prompt in each step is ready to copy into the same Codex project/chat. Complete the project brief once; later prompts read it. Supply real URLs and contacts in that brief, not in every prompt. Keep access secrets elsewhere.

Each step has a recovery prompt. Paste it when the stated check fails, adding the actual error text and authorized screenshots or files. Remove private data before sharing evidence.

Codex may execute through available authorized tools. If WordPress control is unavailable, it should prepare the content and give you a specific manual action. You perform that action in WordPress, return the observed result, and continue. Do not pretend this manual fallback is automatic backend access.

For every step, maintain docs/progress.md with: completed work, evidence, actual time, failures, remaining decisions, and next step. If a new chat is necessary, use the resume prompt in Appendix A.

Step 1 Open the computer and prepare the workspace

Allowance: 0.5 hour.

You do

Open Codex, choose a local project/workspace, and create or select a dedicated folder named lumenbridge-website in a location you control. Avoid choosing your entire Documents folder or an unrelated repository as the project root. Open a browser and sign in to the authorized WordPress test installation.

Codex project-opening controls vary by surface. Select the folder through the app's supported controls; do not guess that a conversation automatically sees your disk.

Codex prompt

Help me establish a workspace for a four-page WordPress website.

Inspect only the selected project directory and available capabilities.
Confirm the absolute project root and existing files before writing.
If this is an unrelated or nonempty project, stop and explain the conflict.
Create only these project folders when safe:
docs, content, assets, wordpress, evidence.

Create docs/progress.md with a Step 1 entry and docs/environment.md.
Record what you can actually read/write/run and whether authenticated
WordPress interaction is available. Do not record credentials.
Do not install software, purchase services, change DNS, or modify WordPress.
Explain any manual setup I must complete and how to verify it.
Done when the workspace and capability report exist and I can open them.

Check before continuing

The Step 1 workspace request is your first Codex prompt. Open both files yourself. Confirm the project root is correct. A report saying WordPress is unavailable is acceptable at this point; an invented claim of access is not.

Likely errors and fixes

  • Wrong directory: select the correct folder; preserve existing files.
  • Permission denied: grant only the relevant supported access or choose an authorized folder.
  • Sign-in prompt: complete it in the intended service, not in chat.

Recovery prompt

Step 1 did not pass. Inspect the actual folder/capability error I provide.
Preserve existing work. Identify the smallest authorized setup correction.
Do not work around a denied permission or claim access you have not verified.
Update docs/environment.md with the result and remaining gap.

Step 2 Set the project working agreement

Allowance: 0.5 hour.

You do

Read the capability report. Paste the following instruction. It establishes the working arrangement for subsequent prompts, not a one-shot command to publish everything.

Codex prompt

Act as my website co-developer and explain unfamiliar steps as we work.
I have a computing background but little practical delivery experience.
Read docs/environment.md and docs/progress.md before continuing.

This project delivers Home, About, Services and Contact in WordPress.
Work in small verifiable steps. Preserve unrelated content and URLs.
Use approved facts only. Record assumptions instead of inventing claims.
Use drafts/test environment until explicit owner acceptance and deployment
authorization are recorded in Step 14.
Do not expose fictional business information as a real public service.
Do not add payments, accounts, booking, tracking, or paid dependencies.

When a tool/action is unavailable, say so. Prepare the local work and give
me the exact manual action, expected result and a way to report it back.
After each task report changed files/pages, actual checks, failures,
remaining decisions and the next step. Never mark unperformed checks passed.
Write these project conventions in docs/working-agreement.md.
Do not modify WordPress yet.

Check before continuing

Read the working agreement. It should preserve the distinction between test work and public deployment. It must not contain blanket access or expenditure authorization.

Likely errors and fixes

  • Codex starts building immediately: stop that direction and point it to this bounded task.
  • It assumes a browser or host connection: require the observed capability evidence.

Recovery prompt

Return to Step 2's scope. Do not publish or make further website changes.
Explain any actions already performed and their verified state.
Correct the working agreement and progress record to reflect actual access.
Continue only with establishing the project conventions.

Step 3 Complete the brief once

Allowance: 1 hour.

You do

For practice, use the fictional facts below and choose a restricted test destination. For a client, replace them with owner-approved information. Do not use the example domain or fabricated contacts as live business details.

Practice facts: LumenBridge Advisory; owner Sara Bekele; offers digital strategy planning and service improvement advice; no approved client names, outcome metrics, testimonials, or partnerships. Desired visitor action: request a discussion. One language. No logo or photographs required; a simple text brand is acceptable. https://lumenbridge.example is illustrative and is not the deployment destination.

Supply the actual test URL and an authorized test contact route before contact testing.

Codex prompt

Create docs/project-brief.md from my supplied information.
Use these fields and ask only for missing essentials:
mode: practice or client
business name and owner
audience and main visitor action
verified facts and approved services
language
test WordPress URL
production URL and operator, if client mode
approved public/test email and phone, with disclosure permission
four page titles and proposed slugs
content/image rights and approval owner
editing approach and maintainer capability
included revisions and acceptance criteria
backup/recovery owner
deployment authority and exclusions.

For practice, use the fictional LumenBridge facts supplied in the runbook.
Do not invent contacts, a deployment domain, credentials, metrics or clients.
Clearly distinguish fictional material from real client material.
Keep missing operational values marked unresolved and do not use them live.
Create docs/decisions.md. Record my choices when I explicitly make them.
Do not modify WordPress yet.

Check before continuing

Confirm the mode, environment, four-page scope, contact values, and who approves. Content can remain draft; unresolved destination/access must be resolved before writing to WordPress.

Likely errors and fixes

  • Missing logo: use an agreed text brand, not an unauthorized image.
  • Client asks for booking: record new scope and exclude it from this run.
  • Multiple languages appear: choose one for this exercise or revise the time/scope.

Recovery prompt

Review the brief for unresolved values, unsupported claims and scope growth.
Separate launch blockers from optional improvements.
Use the smallest four-page scope and list the exact decisions I must make.
Do not silently substitute example contact values or domains.

Step 4 Verify WordPress and a recovery route

Allowance: 1.5 hours.

You do

Open the actual test dashboard. Record whether it is new or existing. Confirm the environment with the operator and arrange a restorable backup before editing existing content. WordPress restoration commonly needs database and files, not only authored text exports. [3]

If Codex cannot inspect WordPress, provide a non-sensitive inventory and screenshots. Do not send account secrets.

Codex prompt

Read the brief and environment report. Inspect the authorized test site
read-only, or guide my manual inspection if direct control is unavailable.
Record site URL, environment, theme, editor/builder, relevant plugins,
existing pages/slugs, publication states and homepage assignment.
Create docs/wordpress-inventory.md and docs/recovery.md.

Identify the backup reference, responsible operator, restoration method,
and a safe recovery verification suitable to the change.
Do not assume admin access proves backups exist.
Do not delete starter/existing content or alter plugins/DNS at this step.
If access or recovery is inadequate, state the blocker and prepare local
content work only; do not claim WordPress setup is complete.

Check before continuing

The actual test environment is identified, current content is recoverable, and the person responsible for restoration is known. Inspect a safe restoration result where feasible. Do not restore over live data as an exercise.

Likely errors and fixes

  • No administrator capability: obtain authorized access or define the manual operator route.
  • Backup cannot be restored: resolve with the operator before risky changes.
  • Existing site has unknown content: capture it and preserve it; do not reset the installation.

Recovery prompt

Diagnose the Step 4 blocker using the supplied observation.
Separate WordPress access, hosting access, backup creation and restoration.
Give the operator a precise request without credentials in the document.
Preserve the baseline and do not advance to WordPress writes until the
necessary destination and recovery arrangements are verified.

Step 5 Prepare truthful page content

Allowance: 1.5 hours.

You do

Provide approved notes or use the practice facts. Identify anything the owner has not confirmed. Review the proposed copy yourself.

Codex prompt

Read the project brief and approved source notes.
Create docs/fact-register.md and content/home.md, content/about.md,
content/services.md and content/contact.md.
For each claim record its source, certainty and approval state.
Write clear visitor-focused content with a single main contact action.
Describe each approved service's audience, approach, deliverables and limits.
Do not invent results, clients, awards, legal status or testimonials.
Use no unapproved contact or images. Mark practice content clearly.
Do not publish. Flag owner decisions and record actual output in progress.

Check before continuing

Every material claim is sourced or explicitly proposed for owner approval. No unfinished placeholders are mistaken for final content.

Likely errors and fixes

  • Inflated language: remove unsupported superlatives and invented proof.
  • Content too long: shorten around visitor questions, preserving facts.
  • Wrong language or terminology: obtain competent review before approval.

Recovery prompt

Edit the four drafts against the fact register.
Remove unsupported claims and preserve uncertainty and dates.
List unresolved approvals separately; do not fill gaps with invented facts.
Show the corrected wording and update the register.

Step 6 Fix the page map and editing approach

Allowance: 1 hour.

You do

Agree four unique slugs and one primary editing approach. A novice-friendly path is the existing supported editor with native blocks where practical. Custom HTML is a bounded alternative, not an excuse to make routine editing impossible.

Codex prompt

Read the approved content and WordPress inventory.
Create docs/page-map.md with four pages, purpose, proposed slug,
navigation label, primary action and exact intended destination.
Preserve useful existing URLs or flag redirect decisions.
Select one maintainable editing approach appropriate to this installation.
Explain how the owner will edit routine text afterward.
If using custom HTML/CSS, scope it and identify how saving and template
behavior will be tested. Avoid adding a framework or paid builder.
Record the chosen approach for my review; do not create duplicates.

Check before continuing

You can explain which page answers each visitor question and how to edit it. A required purchase or significant architectural change needs a separate decision.

Likely errors and fixes

  • Duplicate Home pages: choose the intended page explicitly.
  • Builder and theme conflict: simplify to the agreed approach.
  • Changed slugs break old links: preserve or plan verified redirects.

Recovery prompt

Reconcile the page map with the actual existing pages and editor.
Identify duplicates and URL risks without deleting anything.
Propose one consistent editing route and the minimum decisions needed.
Update the map only after recording the chosen resolution.

Step 7 Define a restrained visual direction

Allowance: 2 hours.

You do

Review a proposed design with actual text lengths. Choose a direction before spending time polishing every page. A text brand and well-organized content are sufficient for this exercise.

Codex prompt

Create docs/design-spec.md for this four-page site.
Specify readable typography, color roles, spacing, content width,
header/navigation, buttons, image policy, focus states and mobile behavior.
Use the approved business character and content, not invented credentials.
Propose one restrained direction with a simple page sketch or supported
local preview. Do not claim a screenshot establishes accessibility.
Prefer lightweight assets and minimal dependencies.
Record what I need to inspect and wait for my design choice before
applying the style across WordPress.

Check before continuing

You understand the hierarchy, primary action, and mobile navigation. Record your choice; owner-facing design decisions should not be inferred from silence.

Likely errors and fixes

  • Large decorative assets dominate: simplify before implementation.
  • Unreadable contrast or small type: change actual combinations/sizes.
  • Design depends on paid assets: replace or obtain separate authorization.

Recovery prompt

Revise only the design issues I identify.
Preserve the approved content and page map.
Reduce visual complexity, explain each change and show the affected
wide/narrow states. Do not introduce unapproved assets or dependencies.

Step 8 Build and save Home

Allowance: 3 hours.

You do

Record the chosen design. Give permission to create/edit the intended test draft, not the live homepage. If using the manual route, create/select that draft in WordPress before pasting content.

Codex prompt

Implement Home from the recorded design and content on the authorized
test draft. Verify the exact site and page identity before writing.
Use the agreed editor. Keep source in wordpress/home and explain how it
maps to WordPress. Do not change a live homepage assignment.

Where direct WordPress editing is available, save as Draft, reopen and
compare the saved result. Where unavailable, prepare the exact block
content or native-block instructions and give me one manual action at a
time, with expected output and confirmation checks.
Respect the template's heading and main-landmark structure.
Scope CSS; do not hide unrelated site elements globally without a
documented layout decision. Verify the result in the actual template.
Report the saved page ID/URL, source, screenshot/evidence and limitations.

Check before continuing

Reopen the editor and preview. The intended content survived saving, appears on the right page, and does not duplicate the template's title or main landmark. “Saved” and a correct front-end preview are separate checks.

Likely errors and fixes

  • Save error or sanitization: preserve local content, inspect capability/version/plugin behavior.
  • Duplicate header/title: resolve template ownership, not random global CSS.
  • Style does not apply: inspect scoping, supported style location, and theme rules.
  • Preview unavailable to the client: use an authorized review route, not publication as a shortcut.

Recovery prompt

Home failed its saved/rendered check. Preserve source and inspect the
exact page identity, error, editor role, template and relevant styles.
Compare intended versus saved content. Reproduce safely on test.
Change one likely cause at a time and verify the result.
Record temporary plugin changes and restore them after diagnosis.
Do not disable unrelated security controls or claim success from syntax
checks alone. Stop and state the gap if safe correction needs an operator.

Step 9 Complete About Services and Contact

Allowance: 2 hours.

You do

Inspect Home first. Then use its approved pattern on the other pages. During the manual route, finish each page and return its observed ID/URL before proceeding.

Codex prompt

Create/update only the three mapped test drafts: About, Services, Contact.
Reuse the approved design and content without fabricating additional proof.
Verify each target identity, save, reopen and preview it.
Keep the authored source under wordpress/about, wordpress/services,
and wordpress/contact.
Connect navigation and contact actions to verified destinations in the
test environment. Identify planned public URLs separately from previews.
Confirm which header/footer is owned by the theme versus page content.
Do not publish pages or change production menus/homepage assignment.
Report all four page identities and any incomplete destination.

Check before continuing

Follow Home → Services → Contact and About → Contact. Pages are complete rather than empty shells. No navigation points to unresolved values.

Likely errors and fixes

  • Link points to production while testing: use the agreed test route.
  • Duplicate page created: stop and reconcile IDs before further writes.
  • Uneven page styles: correct the shared pattern rather than copying new overrides.

Recovery prompt

Reconcile the four-page inventory with the page map.
List each actual ID, state, URL and navigation target.
Fix wrong links or inconsistent shared styles on the authorized drafts.
Do not delete duplicates or overwrite unknown content without a specific
resolution. Repeat the complete visitor journey and record results.

Step 10 Verify contact and media

Allowance: 1.5 hours.

You do

Confirm contact values and disclosure permission. Use authorized test values in practice mode. If the client requires a form, arrange delivery configuration and allow more time if necessary.

Codex prompt

Verify the contact route defined in the brief.
For email/phone links check exact destinations and explain that a link
opening an app does not prove message delivery or a completed call.
Do not add a form merely to make the page look complete.
If a form is explicitly included, inspect required/error/success states
and verify synthetic message receipt with the authorized operator.
Use no private customer data in tests or evidence.

Verify each image/file is approved, loads correctly, and has suitable
presentation and alternatives. Do not publish a supplied private CV.
Record contact and media results in docs/contact-media-checks.md.
Mark failures or unavailable tests honestly.

Check before continuing

The agreed contact mechanism works within its stated scope. For a form, actual receipt is verified. Practice contacts are not public business claims.

Likely errors and fixes

  • Form success but no receipt: inspect destination, mail configuration, logs and spam handling with the operator.
  • Broken PDF/image: verify actual uploaded URL, file identity and access.
  • Phone/email typo: correct from approved source, not a guessed value.

Recovery prompt

Diagnose the specific contact/media failure using authorized evidence.
Separate presentation, destination configuration and actual delivery.
Do not send real personal data or invent a successful receipt.
Correct and retest, or record the missing operator/service dependency.
Do not quietly replace a required form with a link without owner agreement.

Step 11 Correct mobile and keyboard behavior

Allowance: 2 hours.

You do

Open the saved site on a phone where possible. Also test a narrow browser viewport. Use the keyboard to follow navigation and activate the contact action.

Codex prompt

Check all four saved test pages at representative wide and narrow widths.
Record the actual viewport/device/browser, not only the requested size.
Inspect wrapping, unwanted document overflow, menu behavior, controls,
images, long text, headings, labels, reading order and visible focus.
Check that theme/page landmarks are not duplicated.
Use the keyboard for the main journey.
Correct observed issues with scoped changes and repeat affected checks.
Save evidence and docs/responsive-access-checks.md.
Do not claim comprehensive accessibility or all-browser conformance.
If browser tools are unavailable, give me an exact manual test list and
record my observed results separately from checks you performed.

Check before continuing

Text remains readable, controls are reachable, and the main journey works without relying on a pointer. Record what was not tested.

Likely errors and fixes

  • Viewport override did not apply: inspect actual width before reporting mobile results.
  • Table/code forces page overflow: contain the element with usable scrolling or simplify the layout.
  • Hidden contact action: correct stacking/layout and retest the saved page.
  • AI says “looks good” without evidence: require a specific test and observation.

Recovery prompt

Reproduce the reported layout/keyboard issue at the actual measured size.
Identify the responsible element or rule and make a bounded correction.
Preserve working pages. Retest saved WordPress output and the affected
visitor journey. State precisely which checks remain unavailable.

Step 12 Run acceptance checks and correct defects

Allowance: 2 hours.

You do

Ask another person to try the main journey without coaching if possible. Consolidate feedback and classify defects versus new scope.

Codex prompt

Create docs/acceptance-results.md for the exact current candidate.
Check owner-approved facts, all page/menu/action links, saved content,
contact/media evidence, responsive/keyboard results, and recovery readiness.
For each criterion record PASS, FAIL or UNTESTED, environment, date,
evidence and verifier. Distinguish my observations from yours.
Fix in-scope defects on test, then repeat affected checks.
List new requests separately; do not expand scope.
Do not mark the candidate ready while material criteria fail or required
checks are unperformed. Prepare a clear owner-review summary.

Check before continuing

Every criterion has an actual result. Corrections were rechecked. Material defects are resolved; nonblocking limits are visible for owner decision.

Likely errors and fixes

  • Old screenshots used as evidence: retest the changed candidate.
  • Client adds another page: price/plan as new scope, not an invisible defect.
  • Test report contains empty “passes”: replace with observations or UNTESTED.

Recovery prompt

Audit the acceptance report against actual evidence.
Remove unsupported passes, identify stale results and prioritize blockers.
Fix only agreed defects and retest the exact changed candidate.
Explain any owner decision needed; do not use confidence as test evidence.

Step 13 Record source and identify the candidate

Allowance: 1.5 hours.

You do

Use Git/GitHub if available and authorized. Do not make private material public to simplify sharing. If Git setup is not ready, preserve a clearly identified local snapshot and record the limitation; complete the agreed source-control requirement before client handover.

Codex prompt

Capture the accepted authored content, styles, safe configuration examples,
page map and instructions without secrets, enquiries or database dumps.
Record what is outside source control: database, media, plugins and host state.
If an authorized repository is available, use its declared branch/PR
workflow and do not overwrite unrelated history or change visibility.
Otherwise prepare a local source snapshot and precise repository setup
instructions; do not pretend GitHub is configured.

Create docs/release-candidate.md with exact source identity, page IDs,
evidence references, limits and candidate version, for example v0.1.0-rc.1.
Do not move published tags or deploy.
Explain how this source becomes saved WordPress content.

Check before continuing

You can locate the candidate and previous accepted source, and explain what a Git revert would not restore. A repository is not a complete WordPress backup.

Likely errors and fixes

  • GitHub sign-in or repository creation unavailable: user completes authorized setup through the service; do not request credentials in chat.
  • Wrong branch/repository: inspect identity before writing.
  • Protection unavailable on plan: record the gap without claiming enforcement or changing visibility.

Recovery prompt

Inspect the source-control failure and preserve local candidate files.
Verify repository/branch identity and actual permissions/capabilities.
Do not force push, expose private material, or invent a repository state.
Give the smallest supported setup/reconciliation action and record its result.

Step 14 Obtain owner acceptance

Allowance: 1 hour of active review coordination; waiting is additional.

You do

Review the actual candidate, not only screenshots. In practice mode you act as the exercise owner and label the decision accordingly. In client mode the real authorized owner must decide.

A valid approval names the candidate, destination, scope, conditions, and approver. Do not copy a fictional person's approval as real authorization.

Codex prompt

Prepare docs/approval-request.md for the candidate.
Separate content acceptance, release readiness, deployment authorization,
and public launch where applicable.
Include exact candidate/source, target URL/environment, contact mechanism,
known limits, backup/recovery reference and rollback triggers.
For practice mode request only the agreed test-site availability.
For client mode identify the real owner decision required for production.
Do not record approval until the authorized person explicitly provides it.
Do not deploy from this request.

Check before continuing

The decision is real, recorded, and applies to the exact current candidate and target. Rejections return to the relevant step. Conditional approval does not permit unmet launch conditions to be ignored.

Likely errors and fixes

  • No owner response: wait; do not treat silence as approval.
  • Candidate changed after review: renew affected checks and approval.
  • Wrong target named: correct the decision before deployment.

Recovery prompt

Reconcile the candidate, target and recorded approval.
Identify missing, expired or invalidated decisions.
Prepare the corrected review request and stop before deployment.
Do not manufacture an approval or transfer it to a changed candidate.

Record the actual decision

After receiving a real decision, paste this prompt and supply its actual details or authorized evidence. Do not fill the fields with the fictional example owner’s approval.

Record this supplied owner decision in docs/approvals.md:
Approver and authority:
Candidate/source identity:
Target and mode:
Decision and conditions:
Date/time and evidence reference:

Check that the decision matches the current candidate and target.
Identify conditions not yet satisfied. Preserve rejection or deferral
accurately. Do not infer approval or proceed to deployment from this
recording task. Update progress with the next authorized action.

Step 15 Apply the approved deployment

Allowance: 1 hour; provider waiting or migration work is additional.

You do

Confirm the operational window and that the operator is available. In a simple same-installation test-to-public workflow, this may mean publishing the approved pages, assigning Home, and updating the intended navigation. A separate-host move requires a provider-specific plan and may exceed this allowance.

Paste the prompt only when Step 14 has an actual authorization record.

Codex prompt

Read the exact Step 14 authorization and candidate record.
Before writing, verify the approved target, current state, source/artifact,
backup/restoration availability, operator and rollback triggers.
If any condition is missing or the destination has unexplained drift, stop.

Apply only the authorized deployment using the supported route.
For manual operation, give one precise action at a time and verify my
reported result before advancing. Do not invent hosting access.
Confirm homepage assignment, page states and intended menus.
Replace review-only URLs with verified final destinations where authorized.
Do not alter DNS, business email records, plugins or paid services unless
the specific change is separately authorized and necessary.

Record actions, operator, times, result and running state in
docs/deployment-record.md. On failure follow the approved recovery route,
verify restoration, and report the real state instead of declaring done.

Check before continuing

The approved content operates at the intended destination. Practice remains appropriately labeled/restricted. A partially applied deployment is unresolved until reconciled or recovered.

Likely errors and fixes

  • Public links still contain preview routes: replace and test authorized final links.
  • Old content appears: check the actual target and caching with the operator; avoid random repeated writes.
  • Partial update: stop, assess, recover or reconcile using the recorded method.
  • Separate-host migration requires more work: revise the plan/time, not the completion claim.

Recovery prompt

Treat this as a deployment incident, not an opportunity to redesign.
Record what was applied, what failed and the current operating version.
Execute only the already authorized recovery or obtain the needed operator
decision. Verify service/content/contact state after recovery.
Preserve evidence and source; do not report successful deployment until
the intended destination is verified.

Step 16 Verify hand over and close

Allowance: 2 hours.

You do

For a real public launch, inspect from a signed-out/private browsing session as well as the editor account. For restricted practice, verify the intended access boundary and authorized reviewer route. Make one routine content edit through the intended owner workflow, then reconcile the final source.

Have the owner demonstrate an edit if that is part of the engagement.

Codex prompt

Perform final verification of the actual deployed destination and mode.
Check all four pages, navigation, contact, approved media, saved content,
access state and known limits. Record who performed each check.
Guide manual checks when tools are unavailable; do not assume public
access from an authenticated preview.

Create docs/handover.md with routine editing steps, account/service owners,
renewals, backup/recovery references, support boundaries and outstanding work.
Include no credentials.
Reconcile source after any final edits and identify the running version.
Create docs/completion-report.md with actual hours and separate:
- verified completed work;
- accepted nonblocking limits;
- unresolved blockers;
- follow-up improvements.

Use DONE—PRACTICE only for a completed verified test-site exercise.
Use DONE—CLIENT only when authorized deployment, final checks and agreed
handover/source requirements are complete.
Otherwise use BLOCKED or IN PROGRESS with the exact remaining action.
Never upgrade the status merely because the planned time is exhausted.

Check before calling the work done

  • Four complete pages operate at the intended destination.
  • The main visitor journey works and the agreed contact mechanism is verified.
  • Saved content and relevant narrow/wide behavior were checked.
  • The source/running version and external-system boundaries are documented.
  • The recovery method and responsible person are known.
  • Required approval, owner training, and handover are complete.
  • No material acceptance or deployment blocker remains.
  • Final status correctly distinguishes practice from client delivery.

Likely errors and fixes

  • Only the logged-in user can see a supposed public page: fix the authorized publication/access state and retest signed out.
  • Owner cannot edit content: provide training or correct the promised editing workflow.
  • Source differs after a last-minute edit: reconcile before completion.
  • Handover lacks renewal ownership: assign it explicitly, not to an assumed maintainer.

Recovery prompt

The final completion check failed.
Identify the exact unmet criterion and return to the relevant step.
Preserve working parts and make the smallest justified correction.
Repeat affected verification, update source/records and reassess the real
completion state. Do not hide the failure in the handover document.

Appendix A Resume after an interruption

Save work before ending a session. Do not depend on chat memory alone.

Resume this project without overwriting unknown work.
Read docs/project-brief.md, docs/working-agreement.md,
docs/environment.md and docs/progress.md.
Inspect the actual current files/site state with available authorization.
Summarize the last verified step, pending actions and any drift.
Do not infer missing approvals.
Continue only with the next uncompleted bounded task, preserving the
recorded scope and separating observed facts from assumptions.

Appendix B Return a manual result to Codex

Use this after a requested dashboard/operator action. Do not paste secrets.

Manual action report:
Step:
Environment and page/service:
Action I performed:
Expected result:
Actual result:
Error text or sanitized evidence:
Anything else that changed:

Evaluate this observation against the step's completion check.
Do not mark unavailable tests passed. Tell me the next single action,
or update the record if this step is genuinely complete.

Appendix C When the time allowance is exceeded

Record actual time, the cause, and the next decision. Separate learning time, in-scope defect correction, external waiting, and new scope. Do not promise a client the title's duration without estimating their actual project.

If a required feature cannot be delivered safely, narrow the scope by agreement, obtain capable assistance, or stop the affected deployment. A website is complete when its defined outcome is verified and handed over, not when an AI finishes generating files.

Appendix D Relationship to the other publications

The companion foundation guide, Building a Professional WordPress Website with Codex, Version 1.0.0, covers business preparation, foundational concepts, estimation and maintenance. Use this runbook for the concrete first build.

The Source Control Operating Model, Practical Guide, and Template Pack, Version 1.0.0, provide deeper control and record examples as separate publications. This four-page exercise does not automatically satisfy stronger controls for consequential applications.

References and license

The prompts are original instructional recommendations, not a verified guarantee of tool availability or end-to-end automation. They were checked for structural completeness and consistency, not executed as a timed learner trial.

[1] OpenAI, Prompting Codex: desired behavior, context, constraints and verification. Capabilities and permissions vary; verify the actual environment.

[2] WordPress, Get started with WordPress: planning and installation/setup orientation.

[3] WordPress, Backups: database/files and restoration planning.

Primary references checked 27 October 2026. Recheck version-specific behavior and provider procedures during implementation.

Copyright © 2026 Henok Ahmed. The original educational text, prompts, tables and checklists in this publication are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You may share and adapt them, including commercially, with appropriate attribution, a link to the license, and an indication of changes. This grant excludes client websites, private materials, third-party software/assets, trademarks and personal data. Those materials retain their respective rights.

Source: https://henokahmed.com/wordpress-24-hour-runbook/

Companion: Version 1.0.0 prompt deck.

Release note: Henok Ahmed approved edition 1.0.0-draft.1 for publication as Version 1.0.0 with its companion prompt deck on 28 October 2026. Release edits activate the approved license, update metadata, and replace links to unpublished guides with status notes. The instructional prompts are unchanged.

Edition record: Version 1.0.0, 28 October 2026 — author-approved publication.

Prior edition: 1.0.0-draft.1, 27 October 2026 — first companion execution runbook with 16 steps, main/recovery prompts, completion checks, and a 24-hour planning allowance.

Practical learning by Henok Ahmed · Educational text, prompts and checklists: CC BY 4.0, subject to stated exclusions.

Back to top ↑