(adapted from MRUnit site)
The website uses the Apache CMS. More detailed documentation is available on the Apache Infrastructure pages including a quickstart guide on the Apache bookmarklet and a reference manual. It is also useful to look at other Apache CMS sites for examples.
Process¶
-
Commit a change to the website's source Markdown files located at Site's trunk. Before committing, test that the site still builds locally by following these instructions.
If deleting a file or changing the name of a file make a trivial edit to lib/path.pm or lib/view.pm to force a full site rebuild. If making a simple edit it is easier to just use the Apache bookmarklet.
-
Wait a few minutes to get the email on the commits list that buildbot has rebuilt the staging website.
-
If the change looks ok, commit the change to the production website by one of the following:
- Using the Apache bookmarklet and selecting Publish site
- curl -sL http://s.apache.org/cms-cli | perl on your local machine
- ssh -t <user>@people.apache.org publish.pl jspwiki <your Apache ID>
Note: you don't need to be an Apache committer to edit this site; non-committers should follow this FAQ, using the anonymous user, to get their proposed changes live.
Posting generated content¶
- Add the path to content/extpaths.txt relative to the extpaths.txt file to prevent the content getting deleted when the staging site is published
- Commit the generated content directly to the production site svn
Style¶
- Try to limit line length to 80 columns, fold -s <filename> on Linux is helpful for limiting line length
- Use links in the [link name][] style rather than [link name][1] because it is more difficult to match up the numbers and removing links causes all the numbers to have to get updated
- Indent with spaces not tabs
- Use * for lists and indent lists by two spaces
JSPWiki v2.10.2