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 asciidoctor page variables #335

Open
maxandersen opened this issue Dec 21, 2024 · 3 comments
Open

support asciidoctor page variables #335

maxandersen opened this issue Dec 21, 2024 · 3 comments

Comments

@maxandersen
Copy link
Member

I have xam.dk that has a mix of markdown and asciidoc on a jekyll site - and for the asciidoc content there is. no frontmatter but instead use of asciidoc variables starting with :page-*

i.e.

= A Journey Down the QRCode Rabbit Hole with 12 Monkeys
:page-layout: post
ifdef::env-github,env-browser,env-vscode[:imagesdir: ../] 

here starts main doc

this allows having the same .adoc file be reused/moved around nicely.

with this roq currently fails.

jekyll docs on it: https://github.com/asciidoctor/jekyll-asciidoc?tab=readme-ov-file#creating-pages

@ia3andy
Copy link
Contributor

ia3andy commented Dec 21, 2024

I am'not sure how we could do this, template rendering (asciidoc) is happening way down the line at runtime. All the data and routing stuff is already done at deployment....

We could parse it manually like frontmatter I suppose but that would be weird no?

@maxandersen
Copy link
Member Author

Yeah - since you'll need to support ifdef/if def for it to be really useful.

@jtama
Copy link
Member

jtama commented Jan 6, 2025

If we do so, we will have to introduce a common mechanism between the 2 asciidoc extensions

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

No branches or pull requests

3 participants