Zola migration#97
Draft
maxkapur wants to merge 12 commits into
Draft
Conversation
Diff here shows an example. Main changes: - yml to toml - sort_order and hidden (my custom attributes) move to [extra] - permalink becomes an entry in aliases
Just to understand how to do this. Will likely need others
This shows that the /assets/ path maps correctly
Seems like the GH upload pages action depends on the normal version of tar
Owner
Author
|
Before I get too attached to this, want to remind myself that Hugo has native support for KaTeX server-side rendering: https://gohugo.io/functions/transform/tomath/ You have to use a specific tag like |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just messing around with a Zola migration. Only copied a few posts and pages into this version of the site; lots of posts will need manual attention to migrate. Adding issues here as I think of them:
{{ site.email }}don't work for content pages in Zola (only works in templates); you need to define shortcodes for this (seemailto()example)$$ ... $$delimiters... Probably we can still make it work but server-side compilation is a bit tricker. Example from a template that does it: https://github.com/aterenin/academic-paper/blob/eb68d9364d8e9d2f960e38acfe8b1aa276b79277/.github/workflows/deploy.yml#L44 I would prefer to use Deno or something to execute the JS locally and avoid the Node dependency. Local builds and GH action builds should work the same waysort_ordercustom functionality?hidden: trueposts. Maybe they should become pages in the end? Part of the motivation for that, IIRC, was to be able to render the formats masterpost as a post (not a standalone page) to make sure the styles were cascaded in the same way. But the current Zola scaffold uses the same template for posts and pages (plan is to just add conditional logic to account for different frontmatter), so this might not be necessary.