-
Notifications
You must be signed in to change notification settings - Fork 10
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
Make sure asciidoc works as expected #169
Comments
@mkouba do we have a qute-web release with it? |
Good issue! |
I will do a release (with both asciidoc and md) tomorrow. It will be |
@mcruzdev would you try to add this: quarkiverse/quarkus-qute-web#106 before the release? |
Okay, we have time! haha |
FYI |
Ok I am giving it a try |
Can I help in any way to make asciidoc a thing in roq ? |
Ok @jtama:
Then you should be ready to try it :) |
Ok I will try that and make a PR once it works. |
So If I had the qute-web-asciidoc to execute tests in the roq-fontmatter it works:
But in the qarukus blog if I had the quarkus-roq-plugin-asciidoc -which is basically an empty shell pulling dependency to qute-web-asciidoc- the adoc content isn't picked up. I have to admin I don't even understand at which point the conversion is done, which is a bit confusing for me. |
Nevermind my previous comment. It works! Let me add docs and test where needed. And I will provide a PR. |
@jtama yeah for now it's an empty shell but we might move the logic to it at some point and also for Markdown.. I am not sure yet, so let's keep the option open.. |
FYI, the scanner processor is generating a new Qute template with the appropriate markup Qute tag, then Qute is doing the rest using the qute-web extension that allow to use asciidoc and markdown tags. |
No description provided.
The text was updated successfully, but these errors were encountered: