The templates for the individual pages are in the svn under site/ in markdown format. You can use an online markdown editor to approximately see how they look like.
We don't have a better solution yet, unfortunately. --sebastian Am 17.04.2014 20:09 schrieb "Andrew Musselman" <andrew.mussel...@gmail.com>: > The content of the "main" part of each page is written in markdown and > parsed by the CMS to render the HTML. I'm not aware of a way to submit > pages except as patches.. > > > On Apr 17, 2014, at 1:52 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > > > > +1 > > > > the project uses Confluence for the wiki. All but commiters are blocked > from editing pages. > > > > This is getting increasingly frustrating. How many tickets and patches > are being passed around now? I can’t follow them all. I haven’t used > Confluence for 4-5 years now but there must be some way to allow edits and > new pages from anyone pending approval to publish? > > > > On Apr 17, 2014, at 4:47 AM, tuxdna <tux...@gmail.com> wrote: > > > > I have seen the instructions here[1], but I am not sure if there is > > any source-code for the documentation for website. > > > > So here are my questions: > > > > * Does Apache Mahout project use any tool to generate website > > documentation as it is now http://mahout.apache.org ? > > > > * Suppose I want to add some correction or edition to current Apache > > Mahout documentation. Can I get a read-only access to the source of > > website, so that I can immediately see how the edits will reflect once > > there are accepted? > > > > I was thinking in terms of the way GitHub pages work. For example if I > > use Jekyll, I can view the changes on my machine, exactly as the will > > appear on final website. > > > > > > Regards, > > Saleem > > > > > > [1] http://mahout.apache.org/developers/how-to-update-the-website.html > > [2] https://pages.github.com/ > > [3] http://jekyllrb.com/ > > >
