01 / 23
Portfolio principles 00–01 min

Your work,
your website,
your next move

Building a journalism portfolio and continuing to learn

Portfolio principles 01–04 min

50 applications.
15 minutes to scan.

A classroom scenario: what earns a click?

  • What kind of journalist are you?
  • What have you actually made?
  • Why should I trust your work?
Portfolio principles 04–06 min

An archive lists.
A portfolio makes a case.

Weak

“Here is everything I’ve ever done.”

Strong

“Here is evidence that I can do this kind of journalism.”

Portfolio principles 06–09 min

Make the evidence easy to see

  • Clarity over cleverness
  • Selection over volume
  • Evidence over adjectives
  • Readability over decoration
  • Honest attribution over inflated claims
Portfolio principles 09–13 min

Which homepage helps you judge the work?

WELCOME TO MY UNIVERSE

Passionate.
Fearless.
Storyteller.

Scroll to discover my journey

01020304050607080910

Project 1 · Project 2 · Project 3…
Roles and contact somewhere below

MIRA RAO · Work / About / Contact

I report on cities
and public money.

Where the ward budget stops

Reporting, analysis & writing · Student story

Reading district health records

Reproducible analysis · Student project

Election results, place by place

Mapping & methodology · Experiment

Email · GitHub · Method notes

Original fictional examples · Projects and findings are illustrative.

Portfolio principles 13–15 min

A stranger opens your website.

  • Who are you?
  • What do you report on?
  • Which project should I read first?
  • How do I contact you?

Discuss: what would that reader still have to guess?

Curate the work 15–17 min

Start with three pieces
you can stand behind.

Choose evidence

  • An original reported story
  • A rigorous analysis
  • A visualisation or interactive

Name its status

  • Published reporting
  • Student assignment
  • Experiment

Technical ambition counts when its purpose and limits are clear.

Curate the work 17–21 min

Six projects. Three places.

  • Municipal spending: reported story with records and interviews
  • A beautiful chart with little analysis
  • District health: reproducible analysis with limitations
  • A basic Python calculator
  • Election map: interactive with a clear method
  • An unfinished scraping experiment

Choose three. Defend what each one demonstrates.

Original fictional examples · Projects and findings are illustrative.

Curate the work 21–23 min

A project description is a small act of reporting.

01

Headline

What is the story?

02

Finding or purpose

What did you establish or investigate?

03

Your contribution

What did you personally do?

04

Evidence & access

Data, method, story and appropriate code links

A software list cannot answer these questions.

Curate the work 23–26 min

Describe the question,
not just the toolkit.

Weak

“Used Python, Pandas, Matplotlib and AI to analyse a government dataset and create insightful visualisations.”

Stronger

“Analysed five years of district-level rainfall records to examine whether monsoon variability was increasing. Cleaned the data in Python, tested annual trends and built interactive charts. The analysis found substantial year-to-year variation but no consistent increase across all districts.”

Original fictional examples · Projects and findings are illustrative.

Curate the work 26–28 min

Be specific about the work you did.

  • “Reported, analysed and wrote the story.”
  • “Cleaned the dataset and built the interactive visualisation.”
  • “Contributed mapping and data analysis to a team investigation.”
  • “Used AI for HTML/CSS and debugging; independently verified the data and wrote the reporting.”

“Built everything using AI-powered data journalism” leaves the role unclear.

Curate the work 28–30 min

Publish only what you can defend.

  • Project links work
  • Sources and methods are accurately described
  • Claims have supporting evidence
  • Collaborators are acknowledged
  • Unfinished work is labelled honestly

The previous class’s standard applies to claims about yourself, too.

Build & publish 30–32 min

A homepage with a clear reading order

[Your name]Work · About · Contact

[Your reporting focus]

[Two sentences: your questions, approach and evidence.]

01
[Strongest story]
02
[Analysis]
03
[Interactive]
[About] · [Email] · [GitHub] · [LinkedIn] · [Optional CV]
Build & publish 32–34 min

Specific interests beat generic enthusiasm.

Weak · illustrative

“Passionate, hardworking and enthusiastic journalism student with a love for storytelling.”

Stronger · illustrative

“I’m a journalism student interested in public policy and accountability reporting. I use data, documents and code to investigate how government decisions affect people’s lives.”

Build & publish 34–37 min

Give the reader a reason—and a way—to inspect.

Student reporting · Fictional example

Road-repair budgets went unspent as residents waited

Share of planned repair spending usedWard A80%Ward B55%Ward C30%

Compared planned and recorded ward spending, then reported why repairs were delayed.

Role
Reporting, analysis and writing
Methods
Municipal accounts, document checks and interviews

Fictional data and findings. Link labels demonstrate placement; they are not real published projects.

Build & publish 37–39 min

HTML + CSS +
GitHub Pages

A simple, fast, readable site is enough.

No framework, paid hosting, custom domain or complex animation required.

Build & publish 39–42 min

From repository to a working URL

  • Create a repository; use a public repo for GitHub Free.
  • Add index.html, style.css and your real project links.
  • Commit and push the files.
  • Settings → Pages → Deploy from a branch.
  • Choose main → / (root) → Save.
  • Wait for deployment; open and test the published URL.

GitHub’s publishing-source guide ↗

Build & publish 42–45 min

Open it on a phone.
Then follow every link.

Desktop squeezed into mobile

Headline buried beneath a giant thumbnail

IMAGE

Tiny text · hidden contact · hover-only navigation

Content reflows

The story comes first

Readable headline, short description, visible role.

Also check image weight, contrast, keyboard access and links without your login.

Keep learning 66–68 min

Give the tutorial a job.

Tutorial treadmill

Watch → Copy → Finish → Forget

Project-driven learning

Ask → Find data → Learn → Analyse → Verify → Publish → Reflect

Tutorials are useful when you return to a real reporting problem.

Keep learning 68–70 min

A roadmap you can actually maintain

  1. Month 1

    Publish portfolio; clean up existing repositories.

  2. Month 2

    Reproduce a published chart from its source data.

  3. Month 3

    Publish a small original data story.

  4. Month 4

    Learn one technique for a reporting question.

  5. Month 5

    Collaborate or contribute to an existing project.

  6. Month 6

    Publish a stronger piece; replace a weaker entry.

An example, not a mandatory sequence. Adjust scope to time, access and reporting needs.

Keep learning 70–72 min

Choose the resource for the task.

DataJournalism.com ↗

Methods · courses, handbooks and reporting resources

Source / OpenNews ↗

Practice & community · how newsroom projects are made

The Pudding ↗

Inspiration · visual form shaped by a story

Datawrapper Academy ↗

Methods · practical chart, map and table guidance

GitHub ↗

Implementation · inspect code, README files and methods

OpenNews community programmes ↗

Keep learning 72–73 min

You can outsource some typing.
You cannot outsource responsibility.

Can accelerate

Syntax · debugging · prototypes · unfamiliar code · alternative implementations

Still your responsibility

Reporting · sources · statistics · ethics · editorial judgment · errors

Keep learning 73–75 min

A live portfolio URL.
A six-month learning plan.

Portfolio

  • 3 projects or clearly labelled WIP entries
  • Specific descriptions and honest roles
  • Working links and contact information

Learning plan

  • 2 skills to develop
  • 2 original project ideas
  • A realistic publishing schedule

The tools will change. Your ability to ask good questions, test evidence and explain what you find should only get stronger.

Instructor notes