I'm including some more links I've found about the CMS. On Jun 14, 2011, at 5:40 PM, Greg Stein wrote:
> Anakia is "sooooo last decade" technology and has some requirements > for everybody that wants to use it (eg. java :-) http://www.apache.org/dev/cms.html http://www.apache.org/dev/cms.html#anakia-phaseout > If the new CMS can be used, then I'd recommend going with that. It > would be nice to get the community working with that today, as it > should be a good tool to use in the long-term. (Anakia gets to be a > pain for larger sites) http://wiki.apache.org/general/ApacheCms2010 http://wiki.apache.org/general/ApacheCms2010#Content_examples > > The CMS is newer than that documentation, which may be why it "prefers" > anakia. > > Please take a look, and I can help with any authz bits or other setup > (just lemme know what I need to do). https://blogs.apache.org/infra/entry/the_asf_cms > > IOW, my +1 is for the CMS. If we find that the community doesn't like > it, then we can make another choice for the long-term site. I think markdown looks pretty cool and easy. It doesn't look too different from Confluence markup. http://daringfireball.net/projects/markdown/syntax +1 for CMS for the website. Regards, Dave > > Cheers, > -g > > On Tue, Jun 14, 2011 at 20:26, Rob Weir <[email protected]> wrote: >> Our website link is: http://incubator.apache.org/openofficeorg/ >> >> Astute observers may notice that nothing is there. I'd like to get a basic >> podling web site up there ASAP, so we can put out the "welcome mat", have a >> place to report status and accomplishments, list committers, etc. As we get >> an issue tracker up and other services up, they would be linked to from this >> site as well. This could transition into the TLP's website, or it could be >> tossed out once we graduate. In either case, I think we want something >> there for now. >> >> I've been reading through the podling documentation and I see there is some >> relevant advice: >> >> http://incubator.apache.org/guides/sites.html >> >> Essentially, the website must meet certain requirements for navigation, >> content, etc. We can use whatever tool we want to generate it, but Apache >> Velocity Anakia >> <http://velocity.apache.org/anakia/releases/anakia-1.0/>appears to be >> preferred. I don't have a strong preference, but it seems to >> me that gaining some familiarity with that tool would be a generally good >> thing for me to do. So I can take a look. >> >> We need to check the source and generated site into SVN. >> >> Any objections to putting the web site here using Velocity Anakia? Would >> these directories conflict with anything that we are importing from the OOo >> source tree? >> >> /site/src >> /site/gen >> >> -Rob >>
