I really like having everything under version control! On Fri, Feb 26, 2010 at 1:19 PM, Sebastian Hennebrueder <[email protected]> wrote: > I have no experience with confluence and can only point out the advantages > of a Jekyll like approach. > > Before I had a Content Management System for my website and switched over to > Jekyll for a number of reasons > > opening a file to edit is faster > in a shell: > myEditor folder/someFile > > finding something in all files is fast > in a shell: > grep -r foo * > > a editor can replace text across all files, A CMS or WIKI can't > > A CMS or Wiki is only fast if the internet connection is fast > > Preview for textile and markdown in TextMate is fast > > Save and continue work later is no problem > > Adding images is faster, just add them to the repository and use them > > Offline writing is possible > > Everything is in a version control system > > To summarize: We need to decide if we want to make editing simpler or > contributing my multiple persons and possibly simpler deployment. > > Considering deployment, I have no issue for my website. I use a hook which > is executed on push of the git repo. It regenerates the website. The > deploying effort is zero. > > With Jekyll we could even adapt it to our needs if required. I am not sure, > if we can modify anything in Confluence. > > -- > Best Regards / Viele Grüße > > Sebastian Hennebrueder > ----- > Software Developer and Trainer for Hibernate / Java Persistence > http://www.laliluna.de > > > > Ulrich Stärk schrieb: >> >> Hi Sebastian, >> >> The Confluence approach has several advantages: >> >> 1. The website gets generated automatically from the wiki contents. Other >> output formats are supported as well. We will have a CMS-like system with >> access control and everything. It might be possible to give out write access >> to contributors who want to help with documentation but don't need access to >> the source repository. >> 2. This setup is well supported at the ASF and widely used by other >> projects (OpenMQ, Wicket, CXF, Directory, Geronimo, ...). >> 3. It requires minimal setup because almost everything is already in >> place. Just some plumbing is needed. >> >> Using Jekyll it will again be necessary to publish the site manually. I >> don't see the advantage to our current approach. >> >> Cheers, >> >> Uli >> >> On 26.02.2010 17:43, Sebastian Hennebrueder wrote: >>> >>> Ulrich Stärk schrieb: >>>> >>>> It has and this is also the recommended approach since documentation >>>> is considered part of the product. Only individuals who have signed a >>>> CLA should be allowed to edit the docs. >>>> >>>> Uli >>>> >>>> On 26.02.2010 15:07, Thiago H. de Paula Figueiredo wrote: >>>>> >>>>> On Fri, 26 Feb 2010 10:01:06 -0300, Ulrich Stärk <[email protected]> >>>>> wrote: >>>>> >>>>>> I guess we will have two versions of the documentation: latest (trunk) >>>>>> and stable (5.1 for now). >>>>> >>>>> +1 to that. Does the wiki has any access control}? If so, we can hava >>>>> the main documentation editable only by committers and have some are >>>>> where people can contribute pages. >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> Hello, >>> >>> there was a discussion thread recently on this topic and though I posted >>> little, I have experimented with other solutions and discussed possible >>> options offline with Howard. >>> >>> I planned to bring my ideas to the mailing list the next days. I have >>> experimented with Jekyll for my new webpages it is a static site >>> generator which is blog aware. It supports rendering of normal pages + >>> blog like pages. The latter could be used for news for example. >>> >>> I wanted to do an experiment with Tapx to see if it could be an >>> alternative. >>> >>> The nice thing is that it provides very nice markup alternatives: >>> textile and markup. Both are somehow Wiki like and very efficient to >>> use. Files can include plain HTML as well and syntax highlighting is >>> supported with Pygments for all kind of source code. >>> >>> Links: >>> Sample of my new website to come with source code highlighting >>> http://test.laliluna.de/articles/jsf-2-evaluation-test.html >>> Jekyll >>> http://github.com/mojombo/jekyll >>> >>> I hope to be able to continue working on this next week. As far as I >>> remember we got stuck, when deciding about the new layout. >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
-- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
