Offline-ready notes · progress saves on this device
Project LibraryStudy workspace →
Courses/Digital Entrepreneurship/Lesson 6

Lesson 6 of 9

Creating a Personal Portfolio

Read the overview in
English overview

Plan and publish a simple personal website that explains who you are, proves what you can do through projects, and gives visitors a clear way to contact you.

2:16 lectureBeginner7 video chapters30 flashcards + 30 questions
Official Binary Tree uploadSenegal Digital Literacy and Digital Entrepreneurship Week 6Published 2026-08-08 · embedded with chapters, checkpoints, deep notes, and a project

Four clear stages

Learn → Project → Check → Finish

Watch and work through the lecture
  1. 1LearnWatch and work through the lectureUse the chapter notebook and answer each video checkpoint.Do this now
  2. 2ProjectBuild an evidence-first portfolioPlan it, create it, then prove it meets the definition of done.Next
  3. 3CheckAnswer all 30 questionsCorrect weak spots using the explanation after each answer.Next
  4. 4FinishMark the lesson completeThen move to Copyright & Protecting Your Work.Next
Course outlineSenegal Digital Entrepreneurship

Interactive lecture

Watch, pause, think, apply.

Plan and build a responsive portfolio that proves your work, explains your decisions, and gives a visitor a safe, clear way to contact you.

0:003 thinking points marked2:16

Numbered markers show where the video will pause. Seeking past one opens the first unanswered check.

Connecting to the lecture…Open on YouTube ↗

Chapter-by-chapter lecture notebook

Everything in the video, organized for learning

The video is a short platform overview. This expanded studio guide supplies the planning, evidence, accessibility, privacy, and testing work needed to turn a template into a professional portfolio.

Source reviewed2:16 lectureReviewed against the public lecture and its English captions; automatic-caption wording was checked against the lesson context.
7

video chapters mapped into notes, examples, and a concrete action.

This is a detailed learning companion reconstructed from the reviewed lecture—not a verbatim transcript.
01
0:00 in the lectureWhy a portfolio matters
What the video is teaching

A portfolio is selected evidence for a specific audience. Define the role or opportunity, the two or three capabilities to prove, and the action a visitor should take.

Include a concise introduction, selected projects, about or experience context, and contact. Remove work that weakens the intended story.

What to noticeEvidence map

Goal: junior web work. Capabilities: responsive layout, accessible interaction, debugging. Each selected project must prove at least one.

Do this before continuing

Write the audience, three capabilities, and desired next action at the top of your plan.

Replay this chapter on YouTube ↗
02
0:17 in the lectureChoose a builder
What the video is teaching

Wix offers a broad visual ecosystem; Carrd suits focused one-page sites; WordPress provides deep themes and plugins with more maintenance; Google Sites supports simple collaborative publishing. Features and pricing change, so check current terms.

Choose from actual requirements: custom domain, number of pages, editing access, forms, language support, performance, exportability, cost, and who maintains it.

What to noticeDecision matrix

Score each builder against must-have requirements rather than counting every optional feature.

Do this before continuing

Build a five-row decision matrix and justify the winning platform in three sentences.

Replay this chapter on YouTube ↗
03
0:26 in the lectureWix setup and AI start
What the video is teaching

Wix offers a broad visual ecosystem; Carrd suits focused one-page sites; WordPress provides deep themes and plugins with more maintenance; Google Sites supports simple collaborative publishing. Features and pricing change, so check current terms.

Choose from actual requirements: custom domain, number of pages, editing access, forms, language support, performance, exportability, cost, and who maintains it.

What to noticeDecision matrix

Score each builder against must-have requirements rather than counting every optional feature.

Do this before continuing

Build a five-row decision matrix and justify the winning platform in three sentences.

Replay this chapter on YouTube ↗
04
0:57 in the lectureTemplates, layout, mobile, and branding
What the video is teaching

For each project explain the problem, audience, constraints, your role, process, final result, evidence, and what you would improve. Credit collaborators and never imply ownership of work you did not do.

Use consistent image treatment, meaningful alternative text, readable type, restrained motion, and a mobile layout that preserves the story order.

What to noticeCase-study sentence

“I rebuilt the registration flow for shared phones, reducing required fields from 12 to 7 after testing with four learners.”

Do this before continuing

Write one complete case study before styling the page.

Replay this chapter on YouTube ↗
05
1:12 in the lectureCarrd and focused one-page sites
What the video is teaching

For each project explain the problem, audience, constraints, your role, process, final result, evidence, and what you would improve. Credit collaborators and never imply ownership of work you did not do.

Use consistent image treatment, meaningful alternative text, readable type, restrained motion, and a mobile layout that preserves the story order.

What to noticeCase-study sentence

“I rebuilt the registration flow for shared phones, reducing required fields from 12 to 7 after testing with four learners.”

Do this before continuing

Write one complete case study before styling the page.

Replay this chapter on YouTube ↗
06
1:30 in the lectureWordPress, plugins, themes, and menus
What the video is teaching

Use only contact details you are comfortable making public. Avoid home addresses, private student information, hidden document permissions, and exposed editing links.

Test navigation, keyboard use, form feedback, mobile overflow, image loading, spelling, and every external link. Schedule a monthly or quarterly review so dates and work remain current.

What to noticeLaunch checklist

A trusted peer completes the primary task on phone and desktop; the owner fixes failures before sharing the URL.

Do this before continuing

Open the portfolio Code Lab, replace starter content with your evidence, and make every automated check pass.

Replay this chapter on YouTube ↗
07
2:00 in the lectureGoogle Sites
What the video is teaching

Use only contact details you are comfortable making public. Avoid home addresses, private student information, hidden document permissions, and exposed editing links.

Test navigation, keyboard use, form feedback, mobile overflow, image loading, spelling, and every external link. Schedule a monthly or quarterly review so dates and work remain current.

What to noticeLaunch checklist

A trusted peer completes the primary task on phone and desktop; the owner fixes failures before sharing the URL.

Do this before continuing

Open the portfolio Code Lab, replace starter content with your evidence, and make every automated check pass.

Replay this chapter on YouTube ↗

Deep explanations

The ideas behind each chapter

Use these sections when the video moves quickly or you need another example.

010:00

Decide what the portfolio must prove

A portfolio is selected evidence for a specific audience. Define the role or opportunity, the two or three capabilities to prove, and the action a visitor should take.

Include a concise introduction, selected projects, about or experience context, and contact. Remove work that weakens the intended story.

Evidence map

Goal: junior web work. Capabilities: responsive layout, accessible interaction, debugging. Each selected project must prove at least one.

Try it now

Write the audience, three capabilities, and desired next action at the top of your plan.

020:17

Choose the simplest maintainable builder

Wix offers a broad visual ecosystem; Carrd suits focused one-page sites; WordPress provides deep themes and plugins with more maintenance; Google Sites supports simple collaborative publishing. Features and pricing change, so check current terms.

Choose from actual requirements: custom domain, number of pages, editing access, forms, language support, performance, exportability, cost, and who maintains it.

Decision matrix

Score each builder against must-have requirements rather than counting every optional feature.

Try it now

Build a five-row decision matrix and justify the winning platform in three sentences.

030:57

Turn projects into case studies

For each project explain the problem, audience, constraints, your role, process, final result, evidence, and what you would improve. Credit collaborators and never imply ownership of work you did not do.

Use consistent image treatment, meaningful alternative text, readable type, restrained motion, and a mobile layout that preserves the story order.

Case-study sentence

“I rebuilt the registration flow for shared phones, reducing required fields from 12 to 7 after testing with four learners.”

Try it now

Write one complete case study before styling the page.

041:30

Publish with safety and a maintenance plan

Use only contact details you are comfortable making public. Avoid home addresses, private student information, hidden document permissions, and exposed editing links.

Test navigation, keyboard use, form feedback, mobile overflow, image loading, spelling, and every external link. Schedule a monthly or quarterly review so dates and work remain current.

Launch checklist

A trusted peer completes the primary task on phone and desktop; the owner fixes failures before sharing the URL.

  • Accurate authorship and credits
  • Safe contact route
  • Mobile and keyboard test
  • Working links
  • Update owner and date
Try it now

Open the portfolio Code Lab, replace starter content with your evidence, and make every automated check pass.

Language of the lesson

Know these ideas

Portfolio
A selected body of evidence supporting a professional claim.
Case study
A structured account of problem, contribution, process, result, and learning.
Website builder
A platform for creating and publishing sites with managed tools.
Plugin
An extension adding capability to a platform such as WordPress.
Responsive layout
A layout adapting to screen space and input method.
Maintenance
Ongoing updates preserving accuracy, security, and usefulness.

Reason like a practitioner

Misconceptions to correct

  • A portfolio is a gallery of everything.Selection and explanation make evidence understandable for a target audience.
  • The builder creates the professional story.Templates provide mechanics; the creator supplies evidence, clarity, and judgment.
  • Publishing is the final step.Testing, maintenance, privacy review, and current information continue after launch.
Transfer challenge

Use the portfolio Code Lab to publish one strong case-study page, pass every check, test it at 390px, and collect evidence-based feedback from one target visitor.

Lesson project · Responsive portfolio

Build an evidence-first portfolio

A responsive portfolio with About, Skills, two project case studies, process evidence, and a safe contact path.

0%0 of 4 checks
Your brief

Sketch a one-page portfolio on paper with About, Skills, Projects, and Contact sections. For one project, write the problem, your contribution, and the result.

  1. 1
    Plan the work

    State the goal, audience or user, and the evidence a strong result needs. Explain how Portfolio changes your plan.

  2. 2
    Build and test

    Sketch a one-page portfolio on paper with About, Skills, Projects, and Contact sections. For one project, write the problem, your contribution, and the result.

  3. 3
    Prove and improve

    Use Information architecture and Call to action to check the result. Record one piece of evidence, one correction, and one improvement you would make next.

Offline referenceRead the independent walkthrough and practice notes

Why this lesson matters

Plan and publish a simple personal website that explains who you are, proves what you can do through projects, and gives visitors a clear way to contact you.

The goal is not to memorize vocabulary. By the end of the lesson, you should be able to use the ideas in a realistic situation, explain the reason for your choices, and check whether the result actually works for the intended person or task.

Learning objectives

  • Explain Portfolio in your own words.
  • Apply Information architecture to a realistic classroom or community example.
  • Connect Portfolio with Call to action when making a decision.
  • Complete the practice task and reflect on one improvement.

Core ideas

1. Portfolio

A curated collection of work that demonstrates skills through evidence, context, process, and results rather than claims alone.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Portfolio changes what you choose, create, or check.

2. Information architecture

The organization and labeling of content so visitors can quickly understand where they are and where to find what they need.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Information architecture changes what you choose, create, or check.

3. Call to action

A specific next step—such as contact, download, or view project—that is clearly visible and easy for a visitor to complete.

In practice: Look for this idea while you complete the lesson task. Pause before each major step and explain how Call to action changes what you choose, create, or check.

How the ideas connect

Start with Portfolio to understand the foundation of the lesson. Use Information architecture to turn that understanding into an action. Then apply Call to action to check the quality, safety, or usefulness of the result. The three ideas are strongest when you can explain their relationship rather than treating them as separate definitions.

Guided walkthrough

  1. Name the goal. In one sentence, write what you are trying to understand, create, or improve.
  2. Make a prediction. Before touching a device, use Portfolio and Information architecture to predict what a strong result should look like.
  3. Complete the task. Sketch a one-page portfolio on paper with About, Skills, Projects, and Contact sections. For one project, write the problem, your contribution, and the result.
  4. Check the outcome. Use Call to action to inspect the result. Ask what worked, what did not, and what evidence supports your judgment.
  5. Explain and revise. Tell a partner what you changed and why. Make one small improvement, then compare the new result with the first one.

Worked classroom scenario

Imagine two learners sharing one device. The first learner is the driver and performs the steps; the second is the navigator and reads the goal, predicts the next step, and checks the result. Halfway through the task, switch roles. Both learners should be able to explain how Portfolio, Information architecture, and Call to action appeared in the work.

If no device is available, complete the same reasoning on paper: sketch the screen or result, label each decision, and describe what you would test when a device becomes available.

Common mistakes and fixes

  • Rushing into the tool: Write the goal and prediction first so every click or step has a reason.
  • Copying without understanding: After each major step, explain it in your own words to a partner.
  • Accepting the first result: Compare the outcome with the goal and make at least one deliberate improvement.
  • Letting one person control a shared device: Rotate driver and navigator roles so both learners think and practice.

Independent practice

Sketch a one-page portfolio on paper with About, Skills, Projects, and Contact sections. For one project, write the problem, your contribution, and the result.

For an extra challenge, adapt the task for a different audience or community need. Write two sentences explaining what changed and which lesson idea guided your decision.

Check your understanding

  1. How would you explain Portfolio to someone new to the topic?
  2. What is one realistic example of Information architecture outside this classroom?
  3. When might Call to action prevent a weak, unsafe, or confusing result?
  4. How are Portfolio and Information architecture connected?
  5. What evidence would convince you that your practice result works?
  6. If you repeated the activity tomorrow, what would you improve first and why?

Key takeaway

Plan and publish a simple personal website that explains who you are, proves what you can do through projects, and gives visitors a clear way to contact you.

You are ready to move on when you can explain the three core ideas, complete the practice without copying, and describe one improvement using evidence from your result.