I think that we should keep the website and the code base separate. Having the generated site that gets published via pubsub in the same location as the website content makes things easier to find and debug.
I recently helped out Apache Mesos with their website and they update the /documentation section of their website with content from the source repo. If you look at the Rakefile in their site dir [1] you can see how it pulls over the current documentation from the source code and updates the documentation from it. I have updated our site to do something similar for our tutorials so we do not have to inject the entire website into the source code. I've also gone ahead and updated our site with the source_inserter filter, modified for our setup, and all is working as expected with the latest version of nanoc. Tutorials are now available on the site [2] and how its accomplished [3]. As for switching generators i'm fine with Nanoc or Middleman. When I initially reworked the website I used Jekyll and spent a fair amount of time jumping through hoops to make the site not behave like a blog. From reading the docs and what Octopress does I think that we would be in a similar situation as we had with Jekyll. Nanoc is working right now and if everyone is happy with it then we can stay as is. -Jake [1]: http://svn.apache.org/repos/asf/mesos/site/Rakefile [2]: http://thrift.apache.org/tutorial/ [3]: http://svn.apache.org/repos/asf/thrift/site/content/tutorial/cpp.md On Tue, Mar 4, 2014 at 6:36 PM, Roger Meier <[email protected]> wrote: > Hi Jake & co! > > I was not aware of middleman, but I will have a closer look at it. > Octopress is the other hot candidate I see on the radar. > > However, I played around with the mentioned source_inserter and it does a > nice job. > See the attached a patch with modified js tutorial and nanoc upgrade. > > What do you think about a short term solution with the nanoc upgrade and > source_inserter? > > thrift_src directory is currently defined within config.yaml, this can be > changed to ./.. if we move site to www folder within source. > The full site could be versioned via regular release process and the > website > will have up-to-date documentation and information consistant with each > release. Development and Documentation in one place will simplify things. > There are some README.md files within source that we can include directly > via include filters and the upcoming cross.md compatibility/feature > overview > generated by the test suite. > > Best! > -roger > > -----Original Message----- > From: Jake Farrell [mailto:[email protected]] > Sent: Dienstag, 4. März 2014 23:47 > To: [email protected] > Subject: Re: [jira] [Closed] (THRIFT-2001) http://thrift.apache.org/Example > "C++ Server" tab is broken > > Hey Roger > I've been working on a version using middleman which I almost have > completed, I've found that it is better at rendering code snippets and docs > than nanoc and the layout and config within middleman is simplified over > what we currently have. Will throw up on my people.a.o account shortly > > -Jake > > > On Tue, Mar 4, 2014 at 5:25 PM, Roger Meier <[email protected]> > wrote: > > > Just fixed this on the web site: > > URL: http://svn.apache.org/r1574224 > > Log: > > content/index.md: no 4 spaces or tab to avoid md double rendering > > content/tutorial/cpp.md: use html entities < and > > > > > Could you verify site compile on your platforms? > > > > I think about a upgrade of nanoc and adding a code snippet include > > filter such as this: > > http://logs.drbig.one.pl/articles/using_nanoc_for_blogging.html > > > > -roger > > > > > > -----Original Message----- > > From: Jens Geyer [mailto:[email protected]] > > Sent: Mittwoch, 12. Februar 2014 20:07 > > To: [email protected] > > Subject: Re: [jira] [Closed] (THRIFT-2001) > > http://thrift.apache.org/Example "C++ Server" tab is broken > > > > Hi *, > > > > I had similar issues with the publishing process lately. Something is > > broken there, I guess. These sporadic erors make the whole process at > > least fragile, if not prone to error. I don't want to switch > > technology just for the fun of it, but I also don't want to live in > > constant fear every time whenever I change sth. on the web site. > > > > $0,02 > > JensG > > > > > > -----Ursprüngliche Nachricht----- > > From: Henrique Mendonça > > Sent: Wednesday, February 12, 2014 7:23 PM > > To: [email protected] > > Subject: Re: [jira] [Closed] (THRIFT-2001) > > http://thrift.apache.org/Example "C++ Server" tab is broken > > > > Thanks again, Jake! > > I didn't get why it was like that again since the markdown file looked > > alright... > > > > > > On 12 February 2014 17:16, Jake Farrell (JIRA) <[email protected]> wrote: > > > > > > > > [ > > > https://issues.apache.org/jira/browse/THRIFT-2001?page=com.atlassian > > > .j ira.plugin.system.issuetabpanels:all-tabpanel] > > > > > > Jake Farrell closed THRIFT-2001. > > > -------------------------------- > > > > > > Resolution: Fixed > > > > > > > http://thrift.apache.org/ Example "C++ Server" tab is broken > > > > ------------------------------------------------------------ > > > > > > > > Key: THRIFT-2001 > > > > URL: > https://issues.apache.org/jira/browse/THRIFT-2001 > > > > Project: Thrift > > > > Issue Type: Documentation > > > > Components: Website > > > > Environment: Chrome, IE, Opera > > > > Reporter: Henrique Mendonça > > > > Assignee: Jake Farrell > > > > Fix For: 0.9.1 > > > > > > > > > > > > The tabs on the homepage's example section doesn't work in any of > > > > my > > > browsers. > > > > Not sure what changed but it must be just html type something like > > that. > > > > > > > > > > > > -- > > > This message was sent by Atlassian JIRA > > > (v6.1.5#6160) > > > > > > > > > > > >
