Add structured publications rendering pipeline#498
Open
tati-micheletti wants to merge 3 commits into
Open
Conversation
Error was being generated as index was missing from the code {{ index . "container-title" }}. in Line 12. Problem should be fixed now.
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
1 participant
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.
This PR introduces a lightweight structured publications workflow for OMF resources.
Key changes:
Adds publications.bib as the canonical bibliography source
Adds CSL-JSON export for Hugo-compatible structured rendering
Adds reusable Hugo partial for publication rendering
Dynamically injects publications into the Awesome Modeling Practices page
Provides downloadable bibliography source for reuse in reference managers
The implementation intentionally keeps scope minimal:
no CSL citation styling engine
no search/filtering
no advanced bibliography infrastructure
This follows the architecture direction discussed in the previous review conversation while avoiding duplicated maintenance across repositories.