Check and improve: verify what “done” means
Review the content, interactions, layout, and file location.
Complete an acceptance check and save a result you can keep editing.
On this page
01Check four aspects
- Content: Is it accurate? Did the page invent names or experiences?
- Layout: Are text, headings, and buttons readable at large and small widths?
- Interaction: Click every link and button and check its purpose.
- Files: Can you find the source and identify the latest version?
These checks are tailored to the personal-page exercise. Reviewing code changes can also help explain what changed; the official documentation describes code-review features.
02Give actionable feedback
Explain where the problem occurs, what you see, and what you want instead. This is an example, not a claim that your page has this problem.
At a browser width of about 390 pixels, the project title on the homepage is clipped. Find and fix the cause while keeping the full text. Recheck that width and a desktop width, then explain what changed and what you verified.
03Save your first result
Keep the practice folder and confirm its location. Before a major revision, make a backup copy. Learn version control as your work grows.
A local preview confirms that you have an inspectable artifact. Hosting, domains, and public access come after the content is ready.
You can now repeat this workflow: choose a folder → describe a task → inspect the output → request a revision → verify it.
Before you move on
Checklist progress stays in this browser. It is not uploaded or synchronized across devices.
References
Product descriptions refer to the official pages below. Exercises, prompts, and checklists were written for this handbook. Source verification date: 2026-10-02.