This is an automated email from the ASF dual-hosted git repository.
dahn pushed a commit to branch staging-site
in repository https://gitbox.apache.org/repos/asf/cloudstack-www.git
The following commit(s) were added to refs/heads/staging-site by this push:
new f702131fc remove old blog special instructions from README.md (#149)
f702131fc is described below
commit f702131fc99fac2194958828cc2ea026c8bda787
Author: dahn <[email protected]>
AuthorDate: Thu Feb 8 11:12:07 2024 +0100
remove old blog special instructions from README.md (#149)
---
README.md | 23 ++++++-----------------
1 file changed, 6 insertions(+), 17 deletions(-)
diff --git a/README.md b/README.md
index ff50a9b55..35037008e 100644
--- a/README.md
+++ b/README.md
@@ -33,6 +33,12 @@ Most changes are reflected live without having to restart
the server.
## Building and Publishing
+It can be useful at times to start anew:
+
+```
+$ yarn clear
+```
+
To build the website run the following:
```
@@ -44,20 +50,3 @@ served using any static contents hosting service. We've
GitHub Actions based
automation that can publish changes merged to 'main' branch being automatically
published to the 'asf-site'.
-### temporary blog only publishing mech
-
-This procedure is obsolete as soon as the site is migrated to docusaurus
completely
-
-1. Build the docusaruas branch locally:
-```
- # checkout the right branch:
- git checkout old-style-blogs
- yarn clear
- yarn install
- yarn build
-```
-2. Then move the `build` directory to some other place, like `mv build ..`
-3. `git checkout -- .` and then checkout `git checkout asf-site` branch
-4. `cd content/` to manually copy artifacts from `../build/` path.
-5. Generally I copy the `assets`, `blog`, `img` and `files` directory in the
content directory from `../../build/`
-6. git add <files> and commit/push to asf-site branch
