I am going to use this page for two purposes:

Current Site Map:

/index
/community
/news
/events
/forums
/download
/faq
/projects
   /openacs
     /bugtracker
     /3
     /4
     
  /dotlrn
  /aolserver
  /new-system

As you can see most of the main content is available right off the root. We have a projects subsection that will have its own subsections for each "project" hosted at openacs.org

---------------------------------------------------------------------------- Planning ahead of time we should probably think in terms of "subsites" when designing the new openacs.org sitemap. Subsites give us the means not only to make different subsites look and feel differently, they also allow us to segregate users and content.

So, which are the the subsites we know we'll need? And are there some future ones that we can think of right now?

It would be nice if we could identify which packages and nodes that probably should appear under any subsite. Unless I misunderstood Don, we could then create a general package from that, so that mounting a new subsite - complete with the standard packages - would be a snap. Of course we should also identify the packages that belong only to the main subsite.

The tree structure of the "model" subsite, and the sitemap as a whole for that matter, must also be agreed upon before we continue...

This is my idea of what the site map may look like. Please change it or add a comment. (olah)

DaveB: lets hold off on subsites. we can use subsections for now. we can always mount he ETP packages inside subsites later if we need to.


/ (Main Subsite - OpenACS)           
  community/
    companies/
    jobs/
    sites/
  directory/
  doc/
  sb/ (schema-browser)

...

START OF GENERAL SUBSITE STUFF
  calendar/ (Release dates etc)
  forums/
  software/
    bugtracker/ (Do we only want to track software? What about docs, site admin duties, etc? Maybe mount it at a higher level...) DaveB: documentation is a "component" of a package. So one bugtracker per project. And docs is one component of that project. For openacs.org, maybe a bugtracker at an openacs.org subsite. 
    download/
  storage/
END OF GENERAL SUBSITE STUFF

...  

  aolserver/ (AOLserer Subsite)
    calendar/
    forums/
    software/
      bugtracker/
      download/
    storage/

...

  dotlrn/ (dotLRN Subsite)
    calendar/
    forums/
    software/
      bugtracker/
      download/
    storage/

...

  commercial/ (OpenACS.com Subsite)
    calendar/
    forums/
    software/
      bugtracker/
      download/
    storage/