What should a finished portfolio demonstrate?
The key idea
A finished student website should show how well its author met a brief, not only how attractive the opening screen looks. For learners comparing web design courses in Sharjah, a portfolio review can reveal whether the finished work contains understandable content, usable navigation and decisions the learner can explain.
Review the completed project with its brief beside you. Define visitor tasks and collect evidence before giving an overall judgment. A screenshot cannot show whether links reach their destinations.
Give the reviewer a visitor task
Use a fictional shared-workspace information site as a practice brief. It describes rooms, capacity limits and an enquiry route. It has Arabic and English versions. It does not take bookings or show real-time availability, and the portfolio must say that it is a demonstration rather than a commissioned business website.
Give a reviewer this task: “Find whether a room can accommodate six people, check what is included, switch language and find how to ask a question.” Do not tell the reviewer which menu item to choose. Watch where they look and ask them to explain uncertain wording.
Record observed behaviour. “The reviewer opened two unrelated pages before finding capacity” is a useful observation. “The design is confusing” is an interpretation that still needs an example. One review cannot represent every visitor.
Use a small rubric with separate completion gates
For each criterion below, use zero for absent or incorrect, one for present but unclear, and two for clearly demonstrated. The twelve-point total helps organise feedback; it is not a professional certification, an accessibility audit or a promise that the site is ready for production.
| Criterion | Evidence for a clear result |
|---|---|
| Brief coverage | Capacity, included facilities and enquiry route match the brief |
| Task completion | The reviewer can finish the stated visit without instructions |
| Navigation | Link labels predict destinations and no required route ends in a dead end |
| Bilingual consistency | Important facts agree and language switching reaches the equivalent content |
| Readability and access | Content remains usable with keyboard navigation and enlarged text |
| Authorship and presentation | The student's contribution and demonstration status are clear |
Keep critical completion gates outside the score. A portfolio containing someone's private contact details without permission should not be made public just because the visual design scored well. Likewise, a prominent link to a missing page must be corrected if that destination is required by the brief. Fix a blocking issue before celebrating the average.
Review the Arabic and English journey together
For a bilingual portfolio intended for visitors in Sharjah, compare facts before judging translation style. If the English version says six people and the Arabic version says eight, the visitor receives two different offers. Check headings, conditions, units and contact instructions, not only the headline.
Follow the language link from a room-detail page. Does it open the same room in the other language or send the visitor to an unrelated starting page? Review how mixed-direction content such as an English room name appears inside Arabic text. The aim is a coherent task across both versions, not identical line breaks.
Try keyboard navigation and make the text larger. W3C design guidance emphasises understandable navigation and identifiable interactive elements. Record where links or content become difficult to use. The resulting feedback should tell the author what needs investigation rather than demand a vague redesign.
Turn findings into a prioritised revision
Suppose an illustrative review finds three issues: room capacities disagree between languages, the enquiry link is broken and the decorative header feels crowded. Correct the conflicting information first, restore the required route, then consider the visual refinement. The first two prevent a dependable visit; the third needs judgment against the brief.
For every correction, keep the observation, the change and the repeat check. Ask the learner to explain why the correction addresses the problem. Repeating the original visitor task after editing is more informative than assuming that changing a file solved the issue everywhere.
Present evidence without overstating the project
Publish only material you created or have permission to use. Replace real customer records, personal messages and private screenshots with clearly fictional examples. If the project was collaborative, identify your own contribution. Do not describe a static enquiry link as a working booking system or invent client results to make the case study impressive.
A strong portfolio entry can be short: the brief, the visitor task, your contribution, one important revision and the remaining limits. This lets someone considering a course or reviewing a student's progress assess the work on its own terms. Clear evidence makes a modest project more useful than an elaborate display whose behaviour nobody has checked.
References and course details
Use these references for further study. The examples and exercises in this article are educational; consult the catalogue for course details.