Github user swill commented on a diff in the pull request:
https://github.com/apache/cloudstack-www/pull/34#discussion_r99875679
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
To serve it locally:
$ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site *
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build
instructions for committers
-
+
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The
script will automatically generate the HTML files and then move them to the
`content` folder.
+
+# Commiting
+Use GitHub PR to make changes. **No one should commit directly to Apache
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is
time to **commit** the changes to **Apache Software Foundation (AFS) remote
repository**. The ASF remote repository for this project is:
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the
**asf-site** branch (pay attention, this is the name of the branch in the
remote repository). **Do not forget**, you also have to commit the same changes
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the
asf-site branch for the site to be served properly; If you use the `build.sh`
script, this steep is already taken care of.
--- End diff --
s/steep/step/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
