incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [2/2] incubator git commit: Create a README to give some instructions on how to get setup with the site. Removed unneeded file.
Date Sat, 17 Jun 2017 21:12:32 GMT
Create a README to give some instructions on how to get setup with the site.  Removed unneeded


Branch: refs/heads/jbake-site
Commit: d1fcec5604321197f3eecc423b238efdb7968a3b
Parents: 9e2a80b
Author: John D. Ament <>
Authored: Sat Jun 17 17:12:24 2017 -0400
Committer: John D. Ament <>
Committed: Sat Jun 17 17:12:24 2017 -0400

----------------------------------------------------------------------        | 28 ++++++++++++++++++++++++++++ |  1 +
 replacements     |  2 --
 3 files changed, 29 insertions(+), 2 deletions(-)
diff --git a/ b/
new file mode 100644
index 0000000..728dffc
--- /dev/null
+++ b/
@@ -0,0 +1,28 @@
+# Apache Incubator Website
+## Prerequisites
+The website is built using JBake and a Groovy template.  The builds for the website do require
internet access.
+- Install JBake from
+- Create an environment variable `JBAKE_HOME` pointing to your JBake installation
+- Ensure that you have a JVM locally, e.g. [OpenJDK](
+## Building & Running the site
+There is a custom `` file that is used to build the website.  You can call it with
any of the [arguments you would pass to jbake](
+The easiest way to use it is to run `./ -b -s` this will start up JBake in a watching
mode as you make changes it will refresh after a short period of time.
+While working with it locally, you'll notice that the site URLs redirect to ``,
to change this edit `` and uncomment the line referencing `localhost`
+## Jenkins Setup
+Commits to the `jbake-site` branch are automatically checked out and built using ``.
 Once this goes live those commits will go against `master`.  The jenkins job can be found
at [](
+The result of the commits are pushed to the `asf-site` branch which are then published using
+## Asciidoctor
+Most of the pages in the site are written using Asciidoctor.  While it is a form of asciidoc
it does have some [syntax differences that are worth reviewing](
+## Groovy Templates
+The site templates are written in groovy scripts.  Even though the files end with `.gsp`
they are not GSP files and do not have access to tag libraries.  You can run custom code in
them, similar to what is done in [homepage.gsp](templates/homepage.gsp)
\ No newline at end of file
diff --git a/ b/
index 66d6b9a..7f4994b 100644
--- a/
+++ b/
@@ -1,4 +1,5 @@
diff --git a/replacements b/replacements
deleted file mode 100644
index 2f62293..0000000
--- a/replacements
+++ /dev/null
@@ -1,2 +0,0 @@
-Input: <a href=('|")(.+)('|")>(.+)</a>
-Output: link:$2[$4]
\ No newline at end of file

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message