Why are Jekyll and Gollum two separate projects?

[erlend-sh]

I'm seeing a lot of developers opting to use Jekyll instead of Gollum as their documentation platform:

• http://jekyllrb.com/docs/home/
• http://docs.jetstrap.com/
• http://docs.basho.com/

and I just don't see two different problems being solved by these two projects. By and large, they appear to be doing the same things:

• Make static pages
• Live on Git
• Liquid templating

Why develop them separately?

[sunny]

Gollum is a wiki-engine, whereas Jekyll builds websites. The biggest difference would be that Gollum gives you access to the whole ancestry of page revisions. That is because it gets all its data directly from Git, whereas Jekyll just reads the data from disk.

Jekyll doesn't come with any front-end HTML, whereas Gollum is a front-end interface. Depending on how you would like your documentation to live you can use Gollum to let people edit it directly on-line or use Jekyll if you want to choose when to build it.

[bootstraponline]

they appear to be doing the same things:

Make static pages
Live on Git

Gollum doesn't make static pages and Jekyll doesn't use Git.