Author: gmazza
Date: Sun Jan 13 13:54:51 2013
New Revision: 1432620
URL: http://svn.apache.org/viewvc?rev=1432620&view=rev
Log:
Updated website build instructions--take #3 (still learning markdown...)
Modified:
roller/cmssite/trunk/content/downloads/edit_website.mdtext
Modified: roller/cmssite/trunk/content/downloads/edit_website.mdtext
URL:
http://svn.apache.org/viewvc/roller/cmssite/trunk/content/downloads/edit_website.mdtext?rev=1432620&r1=1432619&r2=1432620&view=diff
==============================================================================
--- roller/cmssite/trunk/content/downloads/edit_website.mdtext (original)
+++ roller/cmssite/trunk/content/downloads/edit_website.mdtext Sun Jan 13
13:54:51 2013
@@ -7,7 +7,7 @@ the Apache Infrastructure pages includin
## Process
- 1. If the changes are structurally significant (many pages removed/added,
etc.),
+ 1. If the changes are structurally significant (many pages removed/added,
etc.),
before committing to staging you may wish to test that the site still builds
locally
by following [these instructions][]. Note you will probably lose the CSS
formatting with local builds due to the way the stylesheets are referenced,
@@ -15,15 +15,15 @@ check instead at staging to ensure style
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.
- 2. Commit a change to the website's source [Markdown][] files located in
+ 2. Commit a change to the website's source [Markdown][] files located in
<a href="https://svn.apache.org/repos/asf/roller/cmssite/trunk";
class="external">
https://svn.apache.org/repos/asf/roller/cmssite/trunk</a>. If you're not a
committer, supplying a patch to our JIRA issue tracker instead will do.
- 3. Wait a few minutes to get the email on the commits list that buildbot
has
+ 3. Wait a few minutes to get the email on the commits list that buildbot has
rebuilt the [staging website][].
- 4. If the change looks ok, publish the change to the production website by
+ 4. If the change looks ok, publish the change to the production website by
* (recommended method) Using the Apache bookmarklet: [Publish site][]
* curl -sL http://s.apache.org/cms-cli | perl on your local machine
