What actually happens when someone uses a website?
Consider a visitor sending a training enquiry. The browser presents controls and helps the visitor enter information. A server-backed application may validate that information, apply rules and store an authorised record. A static site can instead prepare a message for an external service, as TWA’s current enquiry flow does. These are different architectures, not different visual styles.
Frontend work concerns what people interact with, including layout, content, keyboard use and feedback. Backend work concerns application behaviour, permissions and data handling. Software development connects those decisions through a system that can be understood, changed and tested. A screenshot cannot show whether that system handles an error correctly.
Make the smallest complete experience first
HTML gives content and controls their structure; CSS describes presentation; JavaScript can add behaviour. Learn native links, buttons and forms before replacing them with custom interactions. Use meaningful names, readable layout and visible feedback. Then practise the difference between checking an input in the browser and enforcing a rule in trusted application logic.
TWA’s existing direction includes frontend, backend, databases, APIs, validation, Git, testing and deployment. Framework selection and a specific backend stack remain part of a learning-plan discussion. MDN’s explanation of clients, servers and HTTP is a useful industry reference for tracing communication, not evidence that TWA promises a particular full-stack syllabus.
Make the pickup page work.
A bakery’s website links to pickup information, but customers see “Page not found.” The information exists at a different address.
Your role: Follow a customer’s request, repair the link and edit a clear message before checking the response.
What you’ll learn: Understand how a browser request reaches a page and brings back content.
No account needed. Nothing is sent or saved. You can restart at any point.
Read the full guided story without the interactive controls
You can follow the same lesson here without JavaScript.
Follow the broken link
Open the pickup link and see which address the browser requests.
What happens and why: The browser requests /pickups. The website has /pickup, so the requested address returns 404: no matching page.
Connect the link to the right page
Choose the address registered by the website, then try the link again.
What happens and why: /pickup matches the route: the mapping between an address and the code that handles it. The reply is 200 OK. Changing a link is different from changing its appearance.
Make the returned message useful
Write a short heading telling the customer this is pickup information. The text is shown as text, never executed as code.
What happens and why: The response now contains the heading you wrote. The server sends content; the browser renders it for the visitor. A clear heading helps people understand the page.
Check the customer’s complete journey
Open the repaired link once more and inspect both the reply status and the displayed heading.
What happens and why: The request matches /pickup, the server replies 200 and the browser displays the updated heading. This small model does not implement a real order form, authentication or payment.
Takeaway: A working page needs a reachable address and understandable content. Trace the request, repair the cause and check the result from the visitor’s view.
Where this is useful: Useful when maintaining website links, forms and customer-facing information.
A fictional educational example, not a confirmed TWA assignment, assessment or learner outcome. Simplified to explore one idea; real situations need context and authorised procedures.
Optional deeper exploration: open the original technical workspace
Want to explore the technical model?
The guided story above introduces the idea. This original workspace lets you try actions in different orders. It has its own reset and does not inherit your story choices.
- Browser
- The application a visitor uses to view a website.
- Route
- A mapping from a requested address to its handler.
- 404
- The website has no matching page for the requested address.
- 200 OK
- The request succeeded; the returned content still needs checking.
Follow a request. Find the boundary.
Learning objective: Trace routing and HTTP responses without confusing browser and server.
A fictional catalogue exposes GET /courses. The server does not implement POST /courses.
Evidence desk
- Browser
- Creates a method and path
- Router
- GET /courses is registered
- Application
- Returns a small catalogue when available
Your workspace
Worked explanation & takeaway — available without JavaScript
GET /courses reaches the registered handler and returns 200. An unknown path returns 404. POST to this known resource returns 405 in this model. An unavailable service returns 503. Real applications also validate inputs and apply authentication and authorisation.
Fictional educational model. No live system, personal assessment or confirmed TWA assignment. All actions run locally in your browser.
Trace the request, not just the screen
The example is conceptual; it does not send information or create an appointment.
- Interface
A person enters a sample request.
- Application rule
Required information and permitted actions are checked.
- Data boundary
Only an authorised server action would persist a record.
- Feedback
The interface reports the actual result.
Explain the issue near the field and preserve useful input. Browser checks help the visitor; a server must still validate a server-backed action.
Read both scenarios and explanations
A required field is missing
Explain the issue near the field and preserve useful input. Browser checks help the visitor; a server must still validate a server-backed action.
The service is unavailable
Show an honest failure or retry state. Do not display “booked” simply because a button was pressed.
An educational illustration using fictional situations. It is not a confirmed TWA assignment, live system, assessment or promise of a particular tool.
A feature includes its failure cases
For a fictional appointment request, sketch the normal path and ask what happens with missing information, a duplicate request, a slow response or an unavailable service. Describe when a user should retry and when retrying could create another record. Do not show a success message until the application has actually completed the action it claims.
A practical development workflow keeps changes in version control, breaks a feature into reviewable pieces and tests behaviour rather than only appearance. Documentation should tell another developer how to run the work, where configuration belongs and what remains unfinished. Small, clear projects make those decisions easier to see than copied interfaces with unexplained code.
A trustworthy appointment-request prototype
Design a small fictional request interface with normal, invalid and unavailable-service states. Use sample information rather than real personal records.
What you could document
- A semantic responsive interface or wireframe
- A request/response diagram and data-field explanation
- A short behaviour checklist for errors and keyboard use
- A README explaining setup, decisions and limitations
What makes the explanation useful?
Look for clear feedback, sensible validation boundaries, keyboard access and an honest distinction between preparing a draft and completing a server action.
The learning plan determines actual activities and assessment. These deliverables are examples, not contractual curriculum outcomes.
Choose a direction by the problems you enjoy
Frontend development may suit an interest in interfaces and accessibility. Backend development may suit rules, APIs and data. Full-stack work connects both, while specialisms can deepen performance, testing or application architecture. These describe types of work to investigate, not roles awarded by completing a page or training plan.
Bring an example of something you would like to build to the conversation with TWA. Discuss your computer confidence, any coding experience and whether you want a foundation or a deeper development route. Enugu-based and international enquiries use the same factual programme description; available arrangements are confirmed individually.