svn commit: r791285 - /websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html

[bu...@apache.org]

Author: buildbot
Date: Mon Jun 20 16:48:24 2011
New Revision: 791285

Log:
Staging update by buildbot

Modified:
    websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html

Modified: websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html
==============================================================================
--- websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html (original)
+++ websites/staging/openofficeorg/trunk/content/openofficeorg/docs/edit-cms.html Mon Jun 20 16:48:24 2011
@@ -62,41 +62,73 @@
     <h1 class="title"></h1>
     <h1 id="how_to_edit_the_openofficeorg_webpages">How to edit the OpenOffice.org webpages</h1>
 <p>This HowTo documentation will show the needed steps to edit the OpenOffice.org
-website. This includes (creation of new pages, modification, and deletion for files
-and sub-directories).</p>
+website. This includes creation of new pages, modification, and deletion - for files
+and sub-directories.</p>
 <h2 id="how_it_works_in_general">How it works in general</h2>
 <p>The website is hosted in a Content Management System (CMS). You will not edit the
 HTML pages directly. The actual edit is splittup in 2 parts:</p>
 <ol>
 <li>
 <p>First you edit the content which is provided as <a href="http://en.wikipedia.org/wiki/Markdown">Markdown text</a> (mdtext).
-    This will be committed into the staging section and automatically build HTML
-    files out of the the mdtext files.</p>
+    This will be committed into the staging section (see the SVN commit mail with
+    your log message) and automatically build HTML files out of the the mdtext files
+    (see the commit mail with "Staging update by buildbot" as log messge).</p>
 </li>
 <li>
-<p>Second you need to publish the staging part to the production section.</p>
+<p>Second you need to publish the staging part to the production section (see the
+    commit mail with "Publishing merge to openofficeorg site by <your ID>" as log
+    message).</p>
 </li>
 </ol>
 <h2 id="what_do_you_prefer_working_via_commandline_or_in_the_browser">What do you prefer: Working via commandline or in the browser?</h2>
 <h3 id="via_commandline">Via commandline</h3>
-<p>coming soon</p>
+<p>It is assumed that you have alsready checked out the code from the SVN repository
+(https://svn.apache.org/repos/asf/incubator/ooo).</p>
+<ul>
+<li>edit the file via your favorite editor like vi</li>
+<li>SVN ci -m"My log message" myfile.mdtext</li>
+<li>execute "http://s.apache.org/cms-cli"</li>
+</ul>
+<p>If this does not work on your local machine just login to people.apache.org and
+  try from here.</p>
+<p>More text coming soon</p>
 <h3 id="editing_in_the_browser">Editing in the browser</h3>
 <h4 id="prerequisites">Prerequisites</h4>
-<h5 id="link_as_browser_bookmark">Link as browser bookmark</h5>
+<h5 id="browser_bookmark">Browser bookmark</h5>
 <p>Normally you see the webpage in your browser. To update this page with an
 inline-editor and little preview you need to add a link as bookmark to your browser
 (more information see <a href="https://cms.apache.org/#bookmark">here</a>).</p>
 <p><a href="javascript:void(location.href=&apos;https://cms.apache.org/redirect?uri=&apos;+escape(location.href))">Add this link as bookmark</a></p>
 <h5 id="apache_id">Apache ID</h5>
 <p>Furthermore, you need an Apache ID to authenticate to the system.</p>
+<h4 id="starting">Starting</h4>
+<p>Browse to the respective webpage or directory you would like to edit and click on
+the bookmark. Now click on the [Edit this directory] link on the top. The following
+is displayed as content from the CMS.</p>
 <h4 id="edit_an_existing_wepage">Edit an existing wepage</h4>
-<p>coming soon</p>
+<p>Click on the actions link [Edit] in the appropriate table cell for editing the
+favorite file. If the file is not in this directory but in a subdir, just click on
+the directory name (e.g., "docs/") to enter this directory.</p>
+<p>Now you should see a new webpage with a 4 fields:</p>
+<ol>
+<li>Upper left is the inline editor for text in markdown syntax.</li>
+<li>Upper right shows the written text as a permanent preview or as HTML source code.</li>
+<li>Below the editor you can enter a log message.</li>
+<li>Enter a general header text, e.g., the license of the entered text.</li>
+</ol>
+<p>When you have finished writing your text, check the "Log message" box, enter a
+commit message and click on [Submit].</p>
 <h4 id="create_a_new_webpage">Create a new webpage</h4>
-<p>coming soon</p>
-<h4 id="delete_a_webpage">Delete a webpage</h4>
-<p>coming soon</p>
+<p>When in th correct directory, at the top enter a name for the new text file (e.g.,
+"my-file.mdtext"). Now you enter your text (see topic above).</p>
 <h4 id="create_new_subdirectory">Create new subdirectory</h4>
-<p>coming soon</p>
+<p>When in the correct directory, at the top enter a name for the new directory (e.g.,
+"my-dir/"). Make sure you entered a trailing "/"!</p>
+<h4 id="delete_a_webpage_or_subdirectory">Delete a webpage or subdirectory</h4>
+<p>When in the corrext directory, click on the actions link [Delete] in the appropriate
+table cell and enter a commit message. Finally click on [Submit].</p>
+<h3 id="links">Links</h3>
+<p><a href="http://www.apache.org/dev/cmsref.html#add-resource">CMS Documentation Reference</a></p>
   </div>
 
   <div id="footer">