You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@velocity.apache.org by cb...@apache.org on 2021/03/10 12:41:14 UTC
[velocity-site] branch main updated: [site] Minor fixes on site
building page
This is an automated email from the ASF dual-hosted git repository.
cbrisson pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/velocity-site.git
The following commit(s) were added to refs/heads/main by this push:
new 8ce190e [site] Minor fixes on site building page
8ce190e is described below
commit 8ce190e54b3e19a3d59fcedb03ae1f5573bd8d09
Author: Claude Brisson <cl...@renegat.net>
AuthorDate: Wed Mar 10 13:41:10 2021 +0100
[site] Minor fixes on site building page
---
src/content/site-building.mdtext | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/src/content/site-building.mdtext b/src/content/site-building.mdtext
index dd733a7..268aa2a 100644
--- a/src/content/site-building.mdtext
+++ b/src/content/site-building.mdtext
@@ -22,25 +22,25 @@ Most of the site sources are in plain markdown, more specifically in [python-mar
This method is by far the easiest one.
1. Clone the site sources
-
-If you are a Velocity commiter, you will want to directly edit the site sources:
-
- :::shell
- git clone https://github.com/apache/velocity-site.git
-
-If you are a contributor, you should first fork the site sources to your github account, and use:
-
- :::shell
- git clone --single-branch --branch master git@github.com:[YOUR_GITHUB_ID]/velocity-site.git
+
+ If you are a Velocity commiter, you will want to directly edit the site sources:
+
+ :::shell
+ git clone https://github.com/apache/velocity-site.git
+
+ If you are a contributor, you should first fork the site sources to your github account, and use:
+
+ :::shell
+ git clone --single-branch --branch main git@github.com:[YOUR_GITHUB_ID]/velocity-site.git
2. Clone the site production pages
-
-As a commiter you will use it to push into production the generated site. As a contributor, you will use it to check locally the result of your changes.
-
-This clone must be called `velocity-site-prod` and must be made in the same directory as the `velocity-site` one.
-
- :::shell
- git clone --single-branch --branch asf-site https://github.com/apache/velocity-site.git velocity-site-prod
+
+ As a commiter you will use it to push into production the generated site. As a contributor, you will use it to check locally the result of your changes.
+
+ This clone must be called `velocity-site-prod` and must be made in the same directory as the `velocity-site` one.
+
+ :::shell
+ git clone --single-branch --branch asf-site https://github.com/apache/velocity-site.git velocity-site-prod
3. Make your changes to the site sources
@@ -49,8 +49,8 @@ This clone must be called `velocity-site-prod` and must be made in the same dire
5. Check the result using your favorite browser
6. Advertize your changes
-
-Commiters have to push the changes in both clones. Contributors only need to submit a pull request to the site sources.
+
+ Commiters have to push the changes in both clones, the source and the production one. Contributors only need to submit a pull request to the site sources.
### Building the site without docker