You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by jo...@apache.org on 2011/07/04 16:18:36 UTC
svn commit: r1142682 -
/incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext
Author: joes
Date: Mon Jul 4 14:18:36 2011
New Revision: 1142682
URL: http://svn.apache.org/viewvc?rev=1142682&view=rev
Log:
period, line wrap
Modified:
incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext
Modified: incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext
URL: http://svn.apache.org/viewvc/incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext?rev=1142682&r1=1142681&r2=1142682&view=diff
==============================================================================
--- incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext (original)
+++ incubator/ooo/site/trunk/content/openofficeorg/docs/edit-cms.mdtext Mon Jul 4 14:18:36 2011
@@ -36,12 +36,13 @@ The general flow for updating the websit
1. You check out the latest version of the web page's source.
1. You edit the page source using [Markdown text syntax][1] (mdtext).
1. You commit the source into the repository. You will see the SVN commit mail with
- your log message
+ your log message.
1. The commit automatically triggers a build that converts the markdown files
-into HTML files in the staging directory. You will see a commit mail with "Staging update by buildbot" as log message).
+ into HTML files in the staging directory. You will see a commit mail with "Staging
+ update by buildbot" as log message).
1. You verify that the staged webpage is correct and then tell the CMS to publish
-the changes to the production directory. (You will see a commit mail with "Publishing merge to openofficeorg site by <your Apache ID>"
- as log message.)
+ the changes to the production directory. (You will see a commit mail with "Publishing
+ merge to openofficeorg site by <your Apache ID>" as log message.)
The intent of this workflow is to allow committers flexibility in changing
webpages and testing changes on a staging website, before moving these changes to