svn commit: r1432616 - /roller/cmssite/trunk/content/downloads/edit_website.mdtext

[gm...@apache.org]

Author: gmazza
Date: Sun Jan 13 13:49:52 2013
New Revision: 1432616

URL: http://svn.apache.org/viewvc?rev=1432616&view=rev
Log:
Updated website build instructions.

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=1432616&r1=1432615&r2=1432616&view=diff
==============================================================================
--- roller/cmssite/trunk/content/downloads/edit_website.mdtext (original)
+++ roller/cmssite/trunk/content/downloads/edit_website.mdtext Sun Jan 13 13:49:52 2013
@@ -1,7 +1,5 @@
 Title: Edit Website
 
-(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
@@ -11,21 +9,25 @@ the Apache Infrastructure pages includin
 
   1. 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>. 
-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.
+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.
+
+If the changes are structurally significant (many pages removed/added, etc.),
+before committing 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, 
+check instead at staging (next step) to make sure stylesheets are working
+as intended.
+
+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. Wait a few minutes to get the email on the commits list that buildbot has
 rebuilt the [staging website][].
 
-  3. If the change looks ok, commit the change to the production website by one
-of the following:
+  3. If the change looks ok, publish the change to the production website by 
 
-    * Using the Apache bookmarklet and selecting [Publish site][]
+    * (recommended method) Using the Apache bookmarklet: [Publish site][] 
     * curl -sL http://s.apache.org/cms-cli | perl on your local machine
     * ssh -t <user\>@people.apache.org publish.pl roller <your Apache ID\>