This is an automated email from the ASF dual-hosted git repository.
carlosrovira pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new 06a49fd Created Release Manger (Web Site) (markdown)
06a49fd is described below
commit 06a49fd2eb5b752c6e2fd05cc060db121477a361
Author: Carlos Rovira <[email protected]>
AuthorDate: Tue Dec 11 23:00:31 2018 +0100
Created Release Manger (Web Site) (markdown)
---
Release-Manger-(Web-Site).md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/Release-Manger-(Web-Site).md b/Release-Manger-(Web-Site).md
new file mode 100644
index 0000000..6ef6d42
--- /dev/null
+++ b/Release-Manger-(Web-Site).md
@@ -0,0 +1,35 @@
+This are the needed steps to perform to publish an update in the Apache Royale
website.
+
+Apache Royale "production" website is in https://royale.apache.org, we have
already a "pre-production" website in https://royale.codeoscopic.com/
+
+Notice that production web is "plain html", and pre site is a "Wordpress
site". So we use a plugin in Wordpress to generate the plain html final site,
making it more performant and secure. Also having a Wordpress site is very
convenient since it gives us a CMS, an interface to easy edit things, and
solves look and feel through WP Themes. As well we can try/test things without
compromise the production site.
+
+People changing things in website must do it through pre-production website.
This is the process:
+
+1. Do as many changes you need through pre site. For that you must enter
wp-admin (https://royale.codeoscopic.com/wp-admin). You must ask for user/pass
in the list. Notice: Is important to know some WP fundamentals and know how we
have organized the site to do changes right.
+
+2. As you have all things correctly changed and published in presite, you need
to generate the plain HTML site. So go to the left side bar WP menu and click
in "Simply Static", then Click Blue big button "Generate Static Files"
+
+3. Wait until the process finish, and click the link that will be know on
screen: "Click here to download"
+
+4. Once you have downloaded the zip, uncompress the file and overlay over your
local repo copy of "royale-website". Notice you MUST be in branch asÃ-site:
https://github.com/apache/royale-website/tree/asf-site
+
+5. Before commit all the delta changes, you need to perform 3 find and replace
operations in all repo to avoid problems in the final site. This is due to the
need of websites to be over https to show it as a secure website.
+
+6. Open your favorite text editor (for example I use BBEdit on Mac) that
allows you to search in all files in the website and replace a string.
+
+7. Search for "http://"; and replace in all website files for "//". But before
execute you must have into account a few exceptions that you can check in the
following image
+
+
+
+8. find **\/\/royale.apache.org\/?p=** and replace with
**https:\/\/royale.apache.org\/?p=**
+
+9. find **"disqusUrl":"\/\/** and replace with **"disqusUrl":"https:\/\/**.
(This will fix Disqus in the production site)
+
+10. Finally you can commit all the changes to the branch, and in few seconds,
the changes should be published automatically to production site
+
+11.- You can check the site in https://royale.apache.org, and ensure your
changes are ok and you see, Disqus widget correctly showing in blog posts and
the secure indicator in your browsers as in the following capture:
+
+
+
+And that's all, you get you release of the Apache Royale website done! Enjoy!
:)
\ No newline at end of file
