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

Add a way to handle parsed markup content before render #118

Open
paradox460 opened this issue Dec 27, 2024 · 0 comments
Open

Add a way to handle parsed markup content before render #118

paradox460 opened this issue Dec 27, 2024 · 0 comments

Comments

@paradox460
Copy link
Contributor

Previously, I had a pre_build extension that would parse the generated html from the markdown parser and output metadata for Table of Contents (ToC) generation. It would be run after the Post and Page extensions, and store its own data in its own key. You could then reference it from a template, and render a Table of Contents.

As of v0.18.0, this no longer works. The problem appears to be that the markup parsing occurs after the build steps, but before the write steps. However, one cannot move the ToC generation, as it is, to pre_write, as the ToC metadata is required to render the templates used by the pre_write step.

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

1 participant