Re: Re-architecting the Community pages

Hi, Scott:

For task forces, we should figure out what we track on vs. what we track on

For adding "Community" to the top-level nav, please see

The proposed categories we settled on are:
* Docs
* Editing (since we really don't have links to "editors" there)
* Discussion
* Blog
* Community Events (so as not to confuse with API events)
This issue has been settle for a while, it just hasn't been implemented. If
we change Community Events to Community, will it loose it's distinction from
Discussion? Among others, Chris Mills (who was the owner in bugzilla) and
Eliot have provided input into this. So we might want to pass any changes by



From:  Scott Rowe <>
Date:  Thursday, March 14, 2013 12:19 PM
To:  julee <>, Jonathan Garbee <>
Cc:  "" <>
Subject:  Re-architecting the Community pages

Hi all,

I'm working on re-architecting the Community pages to provide better
navigation through our Meetings, Task Forces, etc.

First, I've added a Meetings page.

Under that I've added pages for all of the task force meetings.

Second, I've added a Task Forces page.

and under that all of the pages for the different task forces.

The idea is to separate the meetings from the task force pages so that we
can use the meetings pages to track meeting agenda and notes, while using
the task force pages for the overall scope of the project.

I was getting quite annoyed at having to remember where all of these pages
were, and it seems they belong in the community pages.

I also moved the Template Corps page under here. If you find any other
community-related pages, please move them into this tree.

These navigation problems are starting to become painful.

Do you think we should create a link to the Community pages in the
navigation bar of our site chrome?


Received on Thursday, 14 March 2013 21:35:23 UTC