Author: joes
Date: Wed Mar 26 12:01:35 2014
New Revision: 1581794
URL: http://svn.apache.org/r1581794
Log:
elide obsolete instructions
Modified:
thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md
Modified: thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md
URL:
http://svn.apache.org/viewvc/thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md?rev=1581794&r1=1581793&r2=1581794&view=diff
==============================================================================
--- thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md
(original)
+++ thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md Wed Mar
26 12:01:35 2014
@@ -6,37 +6,21 @@ kind: doc
The thrift website is made up of markdown files and templates and uses the
[Apache CMS](http://www.apache.org/dev/cms).
### Website Development
-#### OBSOLETE: there are NO prerequisites for working productively with the
CMS. Publishing the site is doable through the [CMS
webgui](https://cms.apache.org/thrift/publish) or via shell command:
+
+Publishing the site is doable through the [CMS
webgui](https://cms.apache.org/thrift/publish) or via shell command:
:::shell
% ssh -t people.apache.org publish.pl thrift
Casual changes to the site are best handled through the [javascript
bookmarklet](https://cms.apache.org/#bookmark). The workflow is to browse the
live site looking for pages in need of repair, then by clicking on the
bookmarklet you will be redirected to an editor for the page in question that
can ultimately commit your changes back to the site and walk you through the
publication process through the webgui.
-Obsolete content follows...
-
-In order to get started developing and testing the Thrift website ruby must be
installed along with the bundler gem.
-
-* Install Bundler:
- * gem install bundler
-* Install all gem dependencies via bundler:
- * bundle install
-* Run any of the following:
- * rake clean - Remove any temporary products
- * rake dev - Watch content folder for changes and autogen the site
- * rake gen - Compile the website templates into a static site
- * rake run - Run the website locally on
[http://localhost:3000/](http://localhost:3000)
-
### Updating Release Versions
+
The current release versioning is kept in the YAML __DATA__ section of the
global "configuration file"
[lib/path.pm](https://svn.apache.org/repos/asf/thrift/cms-site/trunk/lib/path.pm).
Update the following values and then following <b>Updating the Website</b>
section below
current_release: "{{ conf.current_release }}"
current_release_date: "{{ conf.current_release_date }}"
### Updating the website
-After you have updated any content or added new markdown files you will need
to commit them to svn to trigger a [CMS
build](http://ci.apache.org/builders/thrift-site-staging) of your changes.
After a few seconds have passed your build will be ready for viewing on the
[staging site](http://thrift.staging.apache.org/). See the previous discussion
for the various approaches to publishing your changes to the live site after
you have verified they are rendering correctly on the staging site.
-Obsolete content follows...
-
-* rake gen (static website is left in the 'output' folder)
-* Check in all the changes
+After you have updated any content or added new markdown files you will need
to commit them to svn to trigger a [CMS
build](http://ci.apache.org/builders/thrift-site-staging) of your changes.
After a few seconds have passed your build will be ready for viewing on the
[staging site](http://thrift.staging.apache.org/). See the previous discussion
for the various approaches to publishing your changes to the live site after
you have verified they are rendering correctly on the staging site.
