Organize, brainstorm and prioritize content to meet portal requirements
= Objective =
Figure out what to keep, what to not keep, and what to add to torproject.org.
= Definitions =
* content means anything that goes on a website, including text that you want to display to users, graphical elements such as banners and pictures, to additional resources (manuals, videos, etc.).
# Methodology
Linda will go talk to each of the stakeholders for each portal of the website, identify their needs, and figure out what content will best serve those needs.
= Results =
**Content for Torproject.org:**
* Tor Browser download link*
* Call for donations and donation link*
* Tor mission statement/what is Tor*
* A detailed about Tor page
* Mission statement
* Vision
* Operations
* Any legalese to talk about Tor and dangers of using Tor
* Organizational stuff:
* Job listings
* Information about the Tor board with bio on each member
* List of current TPI employees
* List of current contractors
* List of financial sponsors
* Legal forms and taxes for transparency
* Press stuff:
* Guidelines to writing about Tor in the press
* Contact information for our communications director
* List of press articles on Tor, filter by country, date, type of publication, and topic (anonymity, censorship, etc.)
* Our social media pages
* Policy on using our public information on wiki/blog/etc
* Affiliations
* Sponsors and donors (like https://www.freebsdfoundation.org/donors/)
* Associated organizations (ooni, library freedom project, tails, etc.)
* Any societies or communities we are officially a part of (Internet defense league? PETS?)
** Content for dev.torproject.org**
* Calendar of project releases, team meetings, and deadlines*
* Mailing lists, wiki pages, and IRC channels*
* List of teams and points of contact*
* Onboarding materials for getting started with each team
* Details on how each team works
* Projects each team is doing
* Roadmap for each team
* List of products we work on:
* Tor Browser
* Onion browser
* Orfox/Orbot
* Metrics page, etc...
* Technical design proposals
* Resources/tutorials
* Tor manual, alpha manual
* Understanding bridges
* Verifying signatures
* Configuring a hidden service
* Installing tor source
* Configuring a relay
* Mactports
* Git repos we are associated with: code, images, etc.
* Tips on how to find your way around projects/code
* Tips on navigating tickets
* How to download the source code
* How to incorporate Tor into your application
* information about trademarks and use of the word Tor
**Content for support.torproject.org**
* Overview of products*
* Tor browser vs onion browser vs orbot/orfox
* Other products that use tor that we know of
* how to install tor*
* Instructions for each OS
* How to resolve common tor browser use errors
* Support FAQs*
* Get tor
* Tor Browser manual
* Tor glossary
* Tor relay operator support
* Tor onion service operator support
* Trademark FAQ
* Abuse FAQ
* Legal FAQ
**Content for community.torproject.org**
* Different ways to volunteer*
* Run a relay for us
* Contribute to our code
* Translate for us
* Help run our community
* Contribute design
* Do research on Tor
* Sign up for to voluntarily test tor for us when we release something
* Outreach*
* Tor teaching materials
* Tor talking materials for presentations
* Tor promotional materials
* Countries where we need the most outreach
* Calendar of events you can attend that will do outreach
* Contacts with local people who are also doing outreach
* What we need help with the most*
* Calendar of events where you can meet the greater tor community
* Community governance documents
* Behavioral guidelines
* Expectations when volunteering for Tor
* Definition of tor community vs TPI
* Information on the community council
issue