-
Notifications
You must be signed in to change notification settings - Fork 148
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
Convert textile to asciidoc #322
Comments
textile
to asciidoc
@mojavelinux Had many of the Guides converted.. ? |
I had converted a few of the guides as a prototype, which I pushed as gists: (some of the content may be out of date by now). @bartoszmajsak I'm assuming you mean pandoc for the conversion to AsciiDoc, right? If I remember correctly, @aslakknutsen, you had hacked together a Textile to AsciiDoc converter. I had also created one, but it's pretty hackish: https://gist.github.com/mojavelinux/4708592 |
Thanks buddy! I will investigate. |
One of the main reasons I had put off switching to AsciiDoc because, at the time, I was still waiting for extensions and custom templates to be merged into Asciidoctor. Now that they are in and mature, you should have all the flexibility you need to create the pages using the exact same HTML, which the current CSS & JavaScript expects. Taking this route could save you from having to mess with that stuff. (In effect, just an input change, not an output change). You also have the option to create custom macros to handle some of the boilerplate content (such as the release info table). (See https://github.com/asciidoctor/asciidoctor-extensions-lab for a bunch of ideas). |
@mojavelinux Yes, forgot about that. I made a RedCloth Formatter that can format Textile to Asciidoc: https://github.com/aslakknutsen/redcloth/tree/asciidoc Don't remember the state, but I think this was one of the test outputs: |
asciidoc
with all its great toolchain can improve the way how we create and render our posts, guides etc. Maybepandoc
can automate it?The text was updated successfully, but these errors were encountered: