Organization Structure

Home (News, client feed, most recent work, featu)
Portfolio

Taxonomy structure:

(Client) Projects
- Client1's Job B
- Client2's Job A
(but probably just the name of the project, not a formula like that)

And then a separate taxonomy, with something like this:

For Client
Public
Private

Or maybe more properly:

Workstep
Incidental documentation

The point is I'd like to attribute code improvements, new discoveries, etc. to the project we were working on when the issue came up (to make it easier to find again and to help us see how we spent our time) but the main view of a project should exclude such miscellaneous notes.

Looking at this division, Drupal projects could use the same taxonomy. We could introduce a third vocabulary for clients themselves. This would differentiate site projects from module projects somewhat, but not completely.

Ah! We would have a vocabulary like this:

Projects
Modules
Related Items
Registration Role
Zing Auction
...
Sites
Agaric Design
COA News on FreeSpeech
Agile Practice Patterns
Amazing Things Auction
...
Install Profiles
Agaric default
Fundraising Auction
...
Themes
Agaric Zen Base
...

And perhaps make multiple parentage possible, and continue on in the same vocabulary:

...
Wordpress Plugins
Morse Institute Library widget
...
Clients
COA News
Amr Elssamadisy
Amazing Things Arts Center
...

Most content on the site would fall into one of the project categories, but the same content would also fall into other categories:

Portfolio
...
Samples
...
Services
...
Examples
...
Tech
Drupal
Programming/Development
Theming
Configuration/Administration
Use
GNU-Linux

Finally, maybe instead of taxonomy based access control, use per-node access control for the occasional internal, Agaric-only content.

Certain content types, such as invoices, should be private by default.