Page Comparison

~awp9 wonders whether these instructions should be out of scope for the website itself. While it is important at a marketing level that it be clear that one can birth a new project, doing so is relatively infrequent, relatively technical, and needs to be kept up to date. It more fluidly connects with the collaboration happening in the wiki than with the static statements of the website. ~awp9's gut reaction is that the website page should be just a stub that links out to what we regard as more wiki than website.

~jayshao argues that a reasonably fluid system for manipulating the website results in a dynamic where location of content is less influenced by how often it changes, and more appropriate to determine based on whether or not it's a collaboratively edited document - as some "official" content is probably better suited to basically a broadcast approach.

Jonathan Markow sez:   Website = Identity, brand, information, marketing, communication outside JASIG, easy answers to frequently asked questions.  Wiki = Collaboration, projects, work-in-progress, documentation.

~jayshao my point being that's an artificial technology driven distinction, instead of an intention-based decision. Providing polished, external consumption vs. working internal consumption is a reasonable distinction. Basing that division on the technology we use to deliver sites seems less meaningful. It is possible to restrict & top-down IA a site in a wiki, just as it's possible to have a non-IA site in any CMS or HTML construction. The question is what roles do we need to fulfill?