Two implemented website examples
Organize the site around the visitor’s question
This evidence map makes the documented page structure inspectable. It is an explanatory artifact, not a claim of measured usability or conversion improvement.
Martin’s Feed: explain a logistics service mix
The documented eleven-page implementation includes service, recruitment, company, location, and policy information. These are page groups, not an invented list of eleven page titles.
| Visitor question | Page group | Purpose |
|---|---|---|
| Which service fits my shipment? | Transportation, warehousing, rail transload, cross-border freight | Explain each offering separately. |
| Can I work here as a driver? | Driver recruitment | Give prospective drivers a distinct path. |
| Who am I contacting, and where? | Company, location, contact, and policy information | Supply context and a next step for inquiry. |
No public production-source link or current deployment address is supplied in this case. The repository remains private.
FAST Strength: compare, inspect, inquire
The implemented public website is directly inspectable on this domain. It retains its own coaching identity and navigation.
- Home introduces coaching and public training examples. The training finder displays selections and clears outdated results after an answer changes.
- Coaching & Pricing explains service options. Expandable packages support narrow screens.
- Results provides public training and competition context.
- Send an Inquiry lets a visitor review the service and message before sending. Opening the page does not submit a message or book a service.
Inspect the original IT 195 coursework HTML on GitHub →
The GitHub link is original coursework, not the current production repository. The software case is separate from this coaching website and remains in development.