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 other input formats #32

Closed
antoyo opened this Issue Apr 7, 2017 · 9 comments

Comments

Projects
None yet
3 participants
@antoyo
Copy link

antoyo commented Apr 7, 2017

Hello.
It would be nice to support other input formats, like asciidoctor.
Hugo supports these formats.
Thanks.

@Keats

This comment has been minimized.

Copy link
Collaborator

Keats commented Apr 8, 2017

Hi,

It's very unlikely that I will add support for more input formats in the near future for a few reasons:

  • no crate for asciidoc and the only crate for rst doesn't seem finished (no docs too) from a quick research on crates.io
  • if there were crates for them, I'd still need to be able to hook into the parser like I'm doing with pulldown_cmark (or fork them) for shortcodes, relative links etc
  • very low priority for me

I see the appeal but I don't think that feature will be coming anytime soon (if it ever comes), especially since it first requires other crates to be written first. I might consider it once gutenberg is more mature but definitely not now.

@antoyo

This comment has been minimized.

Copy link
Author

antoyo commented Apr 8, 2017

I am interested in writing a crate for parsing asciidoctor.
Do I need to write it in a specific way so that you can easily integrate it in gutenberg?

@Keats

This comment has been minimized.

Copy link
Collaborator

Keats commented Apr 8, 2017

The way https://github.com/google/pulldown-cmark works very well.
I can easily extend the parser like in https://github.com/Keats/gutenberg/blob/master/src/markdown.rs#L121. Basically if I can hook into the renderer it should be ok

Keep in mind though that inputs other than markdown are not going to be added until all the important features are nailed: i18n, pagination, deploy and probably some stuff I haven't thought of yet so that's a few months away at best.

@antoyo

This comment has been minimized.

Copy link
Author

antoyo commented Apr 8, 2017

Ok, I'll wait a couple of weeks before writing such a parser, then.

@antoyo

This comment has been minimized.

Copy link
Author

antoyo commented Jul 10, 2017

Just to keep you informed: I started to work on the asciidoctor parser.

The HTML generator is implemented with a trait, so you should be able to change the result the way you want.

Please note that the API will change as I'm experimenting with different designs.

@5paceToast

This comment has been minimized.

Copy link

5paceToast commented Apr 1, 2018

Markdown (even the extended variants) is relatively limited.
I think supporting at least one more complete format is preferable, considering the goal of the project is static site generation, rather than just a blogging platform.
For example, I am also a writer, and I write in asciidoc(tor), since that format is the best suited for it (it's actually compatible with docbook, making it not too far from latex without tex commands) - if I wanted to publish readable versions on a website, I simply couldn't use gutenberg.
For project websites, I find asciidoc also helps with writing more complete documentation, once you outgrow basic markdown - similar issue here.

All of this is basically to say that adoc support is a dealbreaker for me, though once that's in I doubt anything further would be required (since gutenberg would be essentially on feature-parity with other generators - in terms of what one can actually do with it, rather than sheer number of entries).

@antoyo

This comment has been minimized.

Copy link
Author

antoyo commented Apr 1, 2018

Just so you know, I haven't worked on my parser for a long time as I work on other projects.
If anyone is inrested to continue it, please tell me.

@Keats

This comment has been minimized.

Copy link
Collaborator

Keats commented Apr 2, 2018

I wouldn't mind addind asciidoc support (but only asciidoc, I don't want to maintain n input) but a few things are required first:

  1. Rewrite the current markdown parser to separate the shortcodes from the markdown (I'm going to work on that next myself)
  2. Have a good, documented working asciidoc crate. @antoyo started one but it would need to be finished
  3. Someone to implement the asciidoc support in Gutenberg. It shouldn't be too hard after 1

@cup cup referenced this issue Feb 19, 2019

Open

AsciiDoc #606

@Keats

This comment has been minimized.

Copy link
Collaborator

Keats commented Mar 26, 2019

I moved the feature request to the forum: https://zola.discourse.group/t/alternative-input-formats/76

@Keats Keats closed this Mar 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.