One final task, with a clear source
Your page has the requested headline and introduction, and its more-details button should now toggle correctly. For the final exercise, add the two FAQ entries specified in SOURCE.md. Keep the project small enough that you can inspect everything it changes.
Use the working copy you saved after review. If you have only read the earlier lessons, the starter ZIP and workbook let you work through the complete exercise later. The ZIP contains the original, deliberately incomplete button behaviour, not a finished solution.
Add a short FAQ section to the fictional workshop page using the two questions and answers in SOURCE.md.
Use keyboard-operable controls, such as native details/summary elements, and match the existing page style. Preserve the corrected headline, introduction, toggle behaviour, event facts and learning-exercise notice.
Keep the project dependency-free. Do not add registration, tracking, payment or external services. Work locally; do not publish.
Review the resulting changes and run the relevant checks in README.md. Report changed files, actual results, checks not run and any unresolved issue. Give me the local preview so I can inspect it.What the finished page should say
The headline is AI at Work: A Practical Starter Session. The introduction says: Practise clear instructions and checking AI drafts in a friendly online workshop.
The date remains 12 November 2026, the time 14:00โ15:00 UTC, the delivery online, and the cost free. These are fictional event facts supplied for practice.
The FAQs explain that no coding experience is required and that this is a fictional learning exercise with no real registration or collection of personal information. A claim of a live event, named sponsor, accredited qualification or attendance guarantee would exceed the source.
Run the final checks
| Check | Evidence to record |
|---|---|
| Content | Headline, introduction, date and time match SOURCE.md. |
| Navigation | See session details reaches the correct section. |
| More-details button | Initial, open, closed and reopened states match the lesson-four table. |
| FAQs | Both source questions and answers appear and can be opened and closed. |
| Keyboard and layout | Controls work without a pointer; a narrow window keeps text and controls usable. |
| Scope | No invented event facts, registration form, tracker or new external service. |
Record pass, fail or not run for each check. If a check fails, give Codex the steps and mismatch, request a focused repair and repeat the affected checks. Use the same acceptance criteria when reviewing the repair.
Write a useful handoff
The handoff should name the changed files, describe the content and behaviour changes, give actual verification results and state what remains to be done. In this small project, index.html and script.js are the likely changed files; any others need an explanation tied to the task.
Keep your current local files and a recoverable version. A local address on your computer is not a link another person can necessarily open. If you later want to share a public site, choose the hosting destination, review the content and data handling, and explicitly authorise that release. Do not equate "looks good locally" with "live on the internet".
๐ญ What would you do?
Choice 1The last line of the handoff
The page looks finished
The handoff says all tests passed, but its details say the browser was unavailable and only the source files were inspected. You have not tried the FAQ or keyboard controls.
Checkpoint
Complete the fictional FAQ task or work through its expected result. Save a handoff with actual checks and limitations, and a recoverable version of the files.
Keep building the habit
The repeatable workflow is: inspect the project, define the task, make a focused change, check the behaviour and review the evidence. Use it for the next small task before adding more tools or a bigger scope.
Continue with Prompt Engineering for clearer briefs, Context Engineering for longer work, and AI Safety for Working Professionals before introducing company information.
This independent course and its fictional project were prepared with official documentation checked on 30 October 2026: quickstart, desktop app, projects, code review, permissions, AGENTS.md, skills and plugins, Codex CLI and pricing. Use the current official instructions when product labels or availability change.
๐ Quiz
Swipe right if this answers the question correctly, left if it does not.
Where do the two final FAQ answers come from?
โAn invented sponsor announcementโ
Is this the right answer?