Wireframes for dev.torproject.org subpages
= Objective =
Design how to lay out the content for dev.torproject.org's subpages:
- dev.torproject.org/teams: putting the team roadmap and projects for each team is actually pretty intense to update/maintain at the website level. Developers also didn't want this, so I think this page can just include detailed descriptions of the teams.
- dev.torproject.org/getting-started: we link to git, irc, and trac on the dev landing banner. I think this page can explain the technology that we use to do the work, organizational-wide. I would like for this to have two functions 1) give a basic overview of what the thing does (i.e. "we use IRC for almost all live communication") 2) link to external links to help them get started (i.e. a tutorial on IRC from irc people) and 3) why we use it (i.e. "Although it's behind the times, we choose it because of these security properties.").
- dev.torproject.org/resources: a page that houses links to all the important manuals and tutorials here. We're not going to create new tutorials or go through the trouble of updating it on the website if they update their link, etc. What's important for this page is that there might be lots and lots of links here, so we should have it organized in a way that people can easily find what they need.
= Definitions =
- wireframes are rough sketches that illustrate the general idea of the design. A wireframe lets you talk about content placement and layout while abstracting finer details such as font, color, styling, and other considerations.
Antonela will independently sketch her best first design of the sub pages, according to previous sitemapping and content organization work. Linda will then review her design, make comments, and Antonela will iterate once before counting it done for this ticket. But this will just result in the initial designs, and these designs will be iterated on some more with feedback from stakeholders.
_Linda will place wireframes here once the task is complete. _