[tor-bugs] #21946 [User Experience/Website]: Architecting a torproject.org with portals with the subsite design pattern

[Tor Bug Tracker & Wiki]

#21946: Architecting a torproject.org with portals with the subsite design pattern
-------------------------------------+--------------------------
 Reporter:  linda                    |          Owner:  linda
     Type:  defect                   |         Status:  assigned
 Priority:  Medium                   |      Milestone:
Component:  User Experience/Website  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:  #21222                   |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+--------------------------
Changes (by linda):

 * status:  new => assigned
 * owner:  hiro => linda


Old description:

> = Objective =
>
> To define the structure of the new website: specifically, to decide how
> many pages/subpages there will be, how the main site will interact with
> its portals/subsites, and deciding where to host content (prioritizing
> important things first, leaving lesser important things in harder-to-
> reach pages).
>
> = Definitions =
>
> * the subsite design pattern looks like this:
>

> This structure is good for organizations with lots of separate
> topics/responsibilities. This is one of many design patterns, which you
> can see [http://adellefrank.com/blog/review-information-architecture-
> patterns here].
>
> = Methodology =
>
> The website will be architected to have a main page (torproject.org) and
> three portals/subsites: 1) dev.torproject.org, 2) support.torproject.org,
> and 3) outreach.torproject.org. The purpose of the main site would be to
> redirect people to the appropriate portals, and the portals will host
> portal-specific content and will not cross-link.
>
> Once we have decided what content will need to be hosted on each page, we
> will architect the website to host the appropriate contents in this
> design pattern.
>
> = Results =
> ''Linda will update this after she's done architecting.''

New description:

 = Objective =

 To define the structure of the new website: specifically, to decide how
 many pages/subpages there will be, how the main site will interact with
 its portals/subsites, and deciding where to host content (prioritizing
 important things first, leaving lesser important things in harder-to-reach
 pages).

 = Definitions =

 * the subsite design pattern looks like this:

 [[Image(subsites-design-pattern.png, 400px)]]

 This structure is good for organizations with lots of separate
 topics/responsibilities. This is one of many design patterns, which you
 can see [http://adellefrank.com/blog/review-information-architecture-
 patterns here].

 = Methodology =

 The website will be architected to have a main page (torproject.org) and
 three portals/subsites: 1) dev.torproject.org, 2) support.torproject.org,
 and 3) outreach.torproject.org. The purpose of the main site would be to
 redirect people to the appropriate portals, and the portals will host
 portal-specific content and will not cross-link.

 Once we have decided what content will need to be hosted on each page, we
 will architect the website to host the appropriate contents in this design
 pattern.

 = Results =
 ''Linda will update this after she's done architecting.''

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21946#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online