Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for asciidoctor #39

Open
EdwinFLopez opened this issue Jul 13, 2016 · 2 comments
Open

Support for asciidoctor #39

EdwinFLopez opened this issue Jul 13, 2016 · 2 comments

Comments

@EdwinFLopez
Copy link

EdwinFLopez commented Jul 13, 2016

Hi all, and thanks for griffin. This is a feature request.
Additionally to markdown, it could be great to support asciidoctor as well by using asciidoctorj.

Totally unrelated rant: I don't know if griffin devs are aware of JBake, but combining the two projects would be an awesome result. From griffing: pagination + taxonomies + ease + handlebars, from jbake: asciidoctor + gradle plugin and support for thymeleaf, freemarker, groovy.

Thank you very much

@pawandubey
Copy link
Owner

I will put asciidoctor on the todo list. I was not planning on supporting multiple input formats because it goes against the principle of simplicity I wanted with Griffin. But since then, I have mellowed down a bit on the issue.

I have heard of JBake. Actually it was after using JBake that I decided to create Griffin. JBake is really good and powerful, but it had a slow parsing process the last time I used it. JBake is great in its own way that it combines multiple technologies and provides flexibility by supporting multiple formats. But that was never the aim of Griffin. That is why I chose Handlebars for simple templating instead of going with the Java templating libraries you mentioned after evaluating them extensively.

Griffin is right now a one-person project 😃

@EdwinFLopez
Copy link
Author

Thanks for your answer and your effort. This project it's really awesome. My motivation to request for asciidoctor is based on the great tooling existent, for instance, diagramming (uml, process, etc) and it's syntax is, in my opinion, a bit more consistent than markdown's. Nonetheless, simplicity is always a good policy. I also believe that less is more. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants