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.
The purpose of this section is to enumerate criteria for tool selection, enumerate some tools matching the criteria on the surface, and then research those tools to see how easy they are to use, as well as how well they work, and how and if we can integrate them into Apache processes and automation.
A good starting point are the various git site repositories located and found at this url https://github.com/apache?utf8=true&q=site where we can research how their sites are built. If anyone knows of some tool they believe works wonderfully for this, then please add them to the list.
Tool Selection Criteria
This criteria should be sorted out on the Apache NetBeans (Incubating) dev mailing list as a series of threads and votes.
TBD
Possible Tools
TBD
Envisioned Generated Site Layout
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.
Process
TBD