= Objective = Write user stories for all four portals to define the content requirements for each page. = Definition = * A user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement. It is a description of a software feature from an end-user perspective. # Methodology Talk with stakeholders of each portal, write user stories. This is a brainstormed list of all the potential users that would visit Tor. We're picking user persons from this set and targeting them in specific portals. * Casual visitor: a person who wants to know a bit about Tor (i.e. Tor Browser users/sponsors). * Curious outsider: a person who is affected by Tor users (i.e. website operators, police). * Journalist: a person who wants to write about Tor (i.e. internet freedom activist). * Researcher: a person who has a lot of technical skills and knowledge (i.e. academics). * Relay operator: a person who runs Tor relays and bridges. * Tor developer: a person who works on Tor (i.e. devs on the network team). * Tor authority: a person who runs a core part of Tor network infrastructure (i.e. directory authority/BridgeDB operators). * Funder: a person that gives Tor money. = Results = **torproject.org** * Audience: first-time Tor users, people curious about Tor, press * Purpose: host critical first-user information and redirect people to the appropriate portals **dev.torproject.org** * Audience: TPI devs, contract/volunteer devs, people who want to volunteer * Purpose: sync all the high-level information about work being done on Tor **support.torproject.org** * Audience: first-time Tor users, relay operators, Tor users with issues * Purpose: help install Tor Browser, resolve common questions, troubleshoot common errors **outreach.torproject.org** * Audience: Tor trainers, Tor speakers, Tor-evangelists on the ground * Purpose: give people excited about Tor what they need to energize more people about Tor