While I use jekyll for lots of stuff (blogs and wicket website), I'd
urge to use asciidoc[tor] as the markup format. Markdown is great, but
rather limited for technical documentation. There is some asciidoctor
integration for jekyll available [1], but I haven't used it in anger.

Just my 2 cts.

Martijn

[1] https://google.com/search?q=jekyll%20asciidoctor


On Thu, Mar 19, 2015 at 4:32 AM, Jason van Zyl <[email protected]> wrote:
> Anyone interested in trying a Jekyll experiment for our website? Extract the 
> useful documentation we believe there is and try to make working on the site 
> a pleasurable experience that is easy for users to contribute to?
>
> I'd like to try this because after this last release I'm frankly tired of 
> looking at our pretty awful website. It's ugly, noisy, unmaintained, hard to 
> navigate and personally just makes me not want to write anything. I would 
> like to like writing documentation again and I think a more standard tool 
> like Jekyll will help. I honestly dislike doing core releases because I have 
> to use the site plugin. I created it, I can hate it and I do hate it.
>
> Even if no one answers I'll try this experiment because I think there's only 
> 10-15 useful documents in the whole site so it likely won't take long.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Takari and Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> There's no sense in being precise when you don't even know what you're 
> talking about.
>
>  -- John von Neumann
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to