Replies: 2 comments 2 replies
-
|
Hey there @laubai and thank you for the feature request! I'm glad you found our community 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Jekyll which Pages natively supports (i.e. if you enable Pages to track a given branch in a repository, it will build with Jekyll) does understand Markdown already. Staying in the Jekyll ecosystem, there is also this plugin for AsciiDoc which you may find helpful: https://github.com/asciidoctor/jekyll-asciidoc. To use this plugin though you will need your own workflow for building and deploying a Pages site. We have an example of such a workflow here. |
Beta Was this translation helpful? Give feedback.
-
|
GitHub else supports asciidoc as a format for all kinds of documentation, why not in GitHub pages? Could it be added to the supported plugins, instead of pushing us to workarounds? |
Beta Was this translation helpful? Give feedback.
-
|
I'm now using my own instance of Jekyll but it takes a lot longer to install, so it uses more resources than if I could use the standard Jekyll, so there is perhaps an ROI? |
Beta Was this translation helpful? Give feedback.
-
I'm sure I'm not the only one who'd like support for asciidoc as well as markdown as a source for GitHub Pages.
If you have recommendations for how to work around the absence of this support in the meantime, I'd love to hear why you recommend them. :)
Beta Was this translation helpful? Give feedback.
All reactions