Smoke test
Open all three HTML pages. Confirm CSS loads, internal anchors work, and no route is broken.
Project memory
This page exists to preserve the reasoning behind the structure, the QA logic, and the content discipline. The portfolio should not drift just because new material gets added later.
Package map
Roles stay separated on purpose. The entry page is not the portfolio. The portfolio is not the documentation.
| File | Role | Reason it exists |
|---|---|---|
| landing.html | Package entry | Controlled entry point for opening the build and keeping user-facing review separate from documentation. |
| index.html | Portfolio surface | Main visitor-facing page with clearer offer, tighter copy, and stronger contact readiness. |
| documentation.html | Browser documentation | Readable project memory for QA, content rules, typography decisions, and next actions. |
| styles.css | Shared style system | One stylesheet keeps the package lighter, more consistent, and easier to maintain before backend. |
QA checklist
Use these checks every time the content changes. The point is to find structural weakness early, not after the project becomes harder to maintain.
Open all three HTML pages. Confirm CSS loads, internal anchors work, and no route is broken.
Review the layout at 320, 375, 768, 960, 1024, and 1440 pixels. Watch for crowding, overflow, and weak spacing.
Replace short text with longer text, add more tags, and swap placeholders with real copy. The layout must survive realistic input.
Ask a fresh viewer what the site is, who it is for, and what action they would take. Confusion is a bug.
Do not deploy with example email addresses, missing handles, or unclear service offers.
Do not ship placeholder project cards where real work should exist. Real proof beats polished filler text.
Typography policy
Typography should help the work read clearly. Beauty without legibility is vanity.
Use serif display styling for key headings only. Keep them strong but readable, not inflated for drama.
Use sans-serif for paragraphs, labels, navigation, and controls. Shorter sentences beat ornamental writing.
Use direct language. Every CTA should describe an action, not merely sound stylish.
Content rules
The structure is stable enough for testing. The next gains come from better content quality and better proof.
Rule 1
Use real visuals, real case summaries, and real outputs wherever possible.
Rule 2
Do not force the visitor to infer what can be commissioned.
Rule 3
One main route and one secondary route are enough for a focused first launch.
Rule 4
Sections must exist because they serve understanding, not because they sound impressive.
Next steps
Backend should come after the content model is stable, not before.
Replace all prototype examples with real projects, real proof, and real contact details.
Before backend, define what counts as a project, a product, an update, and a category.
Add interactivity and data logic only when there is a concrete operational need for them.