Interim Plan For Site Maintenance

Reasoning

Until we have tools selected and a process for editing the site, we need to limit patterns or idiom leak, the number of people editing the site, and the amount of new content moved into the site. This section is to have at least some interim process. This process can be hashed out in a series of email threads and votes on the Apache NetBeans (Incubating) dev list.

Process

TBD

Site Generation/Build Tools

Reasoning

Why would we want a site generation/build tool versus statically maintaining a site? Branding and time. Imagine we had to edit X number of files to replace a footer or header versus editing a single file. What if we had to edit X pages just to replace the site logo? This would be horribly time consuming, and as we grow here at Apache will become great overhead impacting accuracy and possibly releases.

...

Before we configure what ever tool is chosen, we should hash out what the layout will be for the generated site. Some of this layout may be derived from conventions of what ever tool we select should we agree this is reasonable, but should be driven by Apache processes of threads and votes on the Apache NetBeans (Incubating) dev mailing list.

TBD

Interim Plan For Site Maintenance

Reasoning

Until we have tools selected and a process for editing the site, we need to limit patterns or idiom leak, the number of people editing the site, and the amount of new content moved into the site. This section is to have at least some interim process. This process can be hashed out in a series of email threads and votes on the Apache NetBeans (Incubating) dev list.

...

TBD