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

Get (links to) "next" and "previous" page #6

Closed
jplatte opened this issue Nov 2, 2023 · 1 comment
Closed

Get (links to) "next" and "previous" page #6

jplatte opened this issue Nov 2, 2023 · 1 comment
Labels
blog.turbo.fish Blockers for porting my own blog to Hinoki

Comments

@jplatte
Copy link
Owner

jplatte commented Nov 2, 2023

Just realized that I use this for my blog and it doesn't really fit into the design I've been going with, where pages in a directory are fully parsed and rendered in parallel.

However, since frontmatter reading and content rendering are independent steps, I think it should be possible to adjust the file processing to submit the content rendering work as a background task and return right afterwards, which would allow a function for getting metadata of the next / previous page to block until all metadata for the directory is available. I am not certain how summaries, which are based on the content, fit into this though. I'll create a separate issue for that.

@jplatte jplatte added the blog.turbo.fish Blockers for porting my own blog to Hinoki label Nov 2, 2023
@jplatte jplatte mentioned this issue Nov 2, 2023
@jplatte
Copy link
Owner Author

jplatte commented Nov 11, 2023

Done in 903b594 🎉

@jplatte jplatte closed this as completed Nov 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blog.turbo.fish Blockers for porting my own blog to Hinoki
Projects
None yet
Development

No branches or pull requests

1 participant