Hello Chris
Thanks for your reply. I had a look to the Apache CMS reference page
[1]. Just a few questions about CMS:
1. How do we edit the CMS content? By editing the "content/*.mdtext"
files in some text editor and committing to SVN, or by using a
dedicated Web editor? I found mention of a bookmarklet to install on
the browser toolbar [2], but the link seems broken.
2. I found the "sis-site-staging" page [3], but how do we view what the
staged web site looks like?
Le 14/07/13 03:16, Mattmann, Chris A (398J) a écrit :
The overall point you're trying to make is that there are several places
of SIS documentation yet we don't have a "unified" web site for it. Suresh
and Ross Laidlaw and Estrada and Hart tried to address the need that we
"need a SIS website" but no one took a step back and tried to design the
website in concert with the docs you are producing in Maven and Jenkins.
So, someone should do that. We should probably start from the "drawing board"
per se, and just sit down and storyboard what the SIS website look and feel
should be, and where things should go, then work to come up with processes
by which the information in those pages is populated.
I created a wiki page here for what could be the main web site structure
(it does not yet contain a proposal):
http://cwiki.apache.org/confluence/display/SIS/Web+site
If anyone wants to edit with ideas, that would be very appreciated :-)
Consequently, should I move the current
"release-management.mdtext" file to a Maven APT file, before edition for
the SIS specificities noticed in previous emails?
I think we can take an incremental approach to this -- if you'd like to maintain
release management as a Maven APT file that's find, but I don't think it should
be "moved" -- more so -- copied might make more sense. Since Suresh I believe
added
the file originally and I know he is more familiar with the CMS than Maven APT
(or at least I think) a copy would solve both problems and let the person most
willing and with the most time to keep the page up to date, and then perhaps
after
a while we deprecate the other page depending on what we see.
Sound correct?
Yes. I will create an API page describing the release process with
content adapted from the current CMS page, and will leave the CMS page
where unchanged for now (we may update it later).
Martin
[1] http://www.apache.org/dev/cmsref.html
[2] https://cms.apache.org/#bookmark
[3] http://ci.apache.org/builders/sis-site-staging
