[CONF] Apache Mahout > How To Update The Website

[Robin Anil (Confluence)]

How To Update The Website Page edited by Robin Anil Changes (2) ... # Commit changes to the website landing page at https://svn.apache.org/repos/asf/mahout/site/new_website/ # Ensure all outgoing links from the landing page to the wiki are working # The site will automatically be exported from svn by a script running in as soon as its committed Grant's crontab on p.a.o on a nightly basis: 04 4 * * * /home/gsingers/bin/exportMahoutDocs.sh > /home/gsingers/bin/mahout.log 2>&1 It takes about 48 hours for the links to propagate. Once the links are updated, change title on the wiki. *NOTE:* The following is deprecated # Install [Apache Forrest|http://forrest.apache.org/] version 0.8. Make sure you have write permissions on the directory where Apache Forrest is installed, the first time your run Forrest it will attempt to create a plug-ins directory and download several plug-ins. Forrest does not work w/ JDK 1.6. This is particularly onerous on a Mac, since Apple seems to think Java 1.5 is the same as Java 1.6. To fix, see http://www.lucidimagination.com/search/document/9343764a89d7e881/can_anyone_publish_the_site_again_when_you_have_a_sec. # Checkout the Mahout site code [https://svn.apache.org/repos/asf/lucene/mahout/site/]. # Change directory to where it was checked out # Run forrest to build current version of documentation to make sure that Forrest was correctly installed. The generated site will be in ./build/site/. # Make your desired website changes to the source files in ./src/ and regenerate the site with forrest. # Run "forrest run" and browse to http://localhost:8888 to review the changes. You should be able to modify the source documents and hit reload on your browser without rebuilding the site. # When you are satisfied with your changes, regenerate the site with forrest by running "forrest site", # *(recursively) copy ./build/site/\* to ./publish, and commit changes to both ./src and ./publish (add any new files first, but exclude the build directory). This step is very important, if you miss it, your changes will not appear on the site after the next step.* # The site will automatically be exported from svn by a script running in Grant's crontab on p.a.o on a nightly basis: 04 4 * * * /home/gsingers/bin/exportMahoutDocs.sh > /home/gsingers/bin/mahout.log 2>&1 Full Content Some Do's and Dont's of updating the wiki Keep the wiki cleanly formatted. Assume the title is of size h1 Try to keep a single page for a topic instead of starting multiple one. If the topics are related, put it under as a child under the similar page. Notify the developers of orphaned or broken links. Use the page title to link pages so that they get correctly updated by when someone changes the title eg: Correct format [Name of the link|How To Update The Website] The following is incorrect. Please change then when you encounter them [Name of the link|http://<path to>/how to update the website.html] To update the pages, update the wiki directly. Do not change the title of top level pages without updating the same on the landing page. How to update the mahout home page (NOTE: You need committer rights to modify the home page.) To update the home page Commit changes to the website landing page at https://svn.apache.org/repos/asf/mahout/site/new_website/ Ensure all outgoing links from the landing page to the wiki are working The site will automatically be exported from svn as soon as its committed Stop watching space | Change email notification preferences View Online | View Changes | Add Comment