-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Alexis edited this page May 15, 2025
·
4 revisions
Welcome to the portfolio wiki!
🎯 Objective:
- Grab attention quickly and make you want to read on.
✅ To do:
- Get straight to the point: specify what it is and what it's for.
- Use concrete, clear vocabulary, even for a non-tech audience.
- Highlight the type of project (showcase site, web app, internal tool...) + target audience if relevant.
🧠 Example:
- “Collaborative task management web application, designed to help small teams track their projects efficiently.”
🎯 Objective:
- Provide context, show that you know how to meet a real need.
✅ To do:
- Explain the need or pain to be solved.
- Place the project in a concrete context (real customer, school project, personal challenge).
- Show that you understand the “why” behind the project.
✅ Useful structure:
- What was the need?
- Why was it important to solve it?
- What were the challenges or constraints (time, budget, techno, UX...)?
🧠 Example:
- “Existing tools were too complex or expensive for small structures. So the objective was to create a simple, intuitive and free solution to enable freelancers or associations to better organize their day-to-day work.”
🎯 Objective:
- Showcase your role, skills and what you've learned.
✅ To do:
- Be concrete and specific: “I've developed...” → OK, but “I developed authentication with JWT and set up a REST API in Express” → better.
- Mention the technologies used, not just a list.
- Highlight the difficulties you encountered and how you overcame them.
- Show that you're thoughtful, even if you're just starting out: technical choices, code organization, time management...
🧠 Example:
- “I developed the interface in React with TypeScript, focusing on component modularity. On the backend, I designed a REST API with Express and MongoDB, and managed authentication via JWT. A major difficulty was managing real-time conflicts between multiple users, which I solved by implementing sockets.”
- Be professional but human: no need for overly formal language, talk as you would to a curious recruiter or colleague.
- Active rather than passive: “I designed”, “I implemented”, “I learned how to...” rather than “A solution was implemented...”.
- Showcase yourself without overselling: demonstrate your involvement and autonomy, but remain humble about your skills if you're just starting out.
- Write clear, informative alternative text, so it can be displayed when opening images in full screen, in addition to screen readers.
- Style : What it is (Maquette, Screen of the site), What it shows (Home page, project page) and How It's Useful (Showing responsive, dark mode, difficult feature, design choice...)