site: depend on shared ecosystem chrome + finder table - #3
Open
seabbs-bot wants to merge 4 commits into
Open
Conversation
Replace the tutorials site's own navbar and footer with the shared navbar/footer HTML partials from the main epiaware.github.io site, pulled in as a git submodule (_shared/site). The single source of truth now lives in the main repo; the tutorials site renders it via include-before/after-body instead of duplicating it. Keep the shared filter-table widget, and port the package-tutorials finder table (search + approach filter + Package column linking to each package's docs). CI inits submodules on checkout.
Point _shared/site at the main-site commit whose shared navbar.html renames Docs to Packages and orders it before Tutorials, so the tutorials chrome matches the ecosystem nav.
Seven links in the hand-authored tutorials table 404d: six ComposableTuringIDModels case studies moved from /case-studies/ to /tutorials/ on the live docs site, and the ConvolvedDistributions "visualising convolutions" tutorial is actually published as "convolving-distributions". Also make the CensoredDistributions package-column links use /stable/ to match the tutorial links in the same rows, and remove the leftover listing: block from the front matter now that tutorials/ only contains the excluded index.qmd.
The shared navbar partial supplies a <div id="quarto-search"> that quarto-search.js hydrates by id, but Quarto only emits search.json and the site_libs/quarto-search/* assets when website.search is truthy. With search: false the box rendered inert, a regression against the config navbar this design replaced. Bump the submodule pin so the site picks up the navbar revision that carries the search markup.
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.
Makes the tutorials site depend on the shared ecosystem chrome instead of carrying its own copy.
Supersedes the approach merged in #2, which inlined a duplicate navbar and footer.
What changed
_quarto.yml— no config-driven navbar or footer. The sharednavbar.html/footer.htmlpartials from the main site repo are injected viaformat.html.include-before-body/include-after-body, pulled in through a git submodule (_shared/site→EpiAware/epiaware.github.io).search: true— the shared navbar carries a<div id="quarto-search">, but Quarto only emitssearch.jsonandsite_libs/quarto-search/*when this flag is set, so withsearch: falsethe box rendered inert. Search is per-site: this indexes the tutorials content only.tutorials/index.qmd— filterable finder table (search + approach filter) with a Package column linking to each package's docs. The filter widget JS is shared from the submodule. All 26 links verified to return 200..github/workflows/publish.yml— checkout inits submodules.Merge order (important): the submodule pins an
epiaware.github.iocommit that currently lives on itsshared-chromebranch (epiaware.github.io#26). That PR must merge first. Repoint the pin to the resultingmaincommit before merging this PR — if #26 is squash-merged and the branch deleted, the current pin becomes unreachable and CI will fail on submodule fetch.Verified with a real
quarto render: one navbar and one footer per page, search assets and index emitted, all 21 table rows rendering, logo resolving at depth.This was opened by a bot. Please ping @seabbs for any questions.