Skip to content

Add generated toolchain, GPU and MPI pages and a Yggdrasil section - #15

Open
ViralBShah wants to merge 1 commit into
masterfrom
vs/toolchains-page
Open

ViralBShah wants to merge 1 commit into
masterfrom
vs/toolchains-page

Conversation

@ViralBShah

@ViralBShah ViralBShah commented Nov 15, 2026 •

Copy link
Copy Markdown
Member

Fixes #2.

Generated pages

All three pages are computed when the site is built (utils.jl), so nobody has to keep them up to date by hand.

  • /toolchains/ comes from BinaryBuilderBase:
    • Compilers: every available GCC, LLVM/Clang, Rust, Go and OCaml version.
    • Platforms: one row per platform in supported_platforms(), showing which GCC, Rust and OCaml versions it has. It uses the same rules as choose_shards with the default LLVM, so gaps show up: riscv64 has only GCC 14 and 15, Apple silicon only 12.0.1-iains and 15.2.0, and x86_64 FreeBSD only 6.1 and later.
  • /gpus/ covers NVIDIA, AMD, Intel, Apple and the cross-vendor OpenCL, Vulkan and SPIR-V:
    • CUDA: every toolkit (20 of 21 built by default, from 10.2 to 13.5) and its x86_64, ARM server (SBSA) and Jetson builds. This comes from Yggdrasil's platforms/cuda.jl.
    • GPU libraries: a curated list per vendor. Each library's latest version comes from the General registry.
  • /mpi/: the 5 MPI implementations, which versions each is compatible with, their latest registered versions, which platforms each is built for, and how users switch between them with MPIPreferences. This comes from Yggdrasil's platforms/mpi.jl.

The homepage's platform count (18), toolchain count (50, which replaces the stale 45), OS list and CPU list come from the same data. The toolchain count is the number of distinct compiler versions: 13 GCC, 17 LLVM, 13 Rust, 6 Go and 1 OCaml.

To answer the question in the issue: the toolchain count isn't platforms × (gcc + llvm). Each LLVM version is a single build that targets every platform, and GCC versions don't cover every platform.

Homepage

  • Bug fix: the rows="27 attribute on the asciinema player was never closed, so the browser dropped the poster setting and the demo started on a blank frame.
  • Two sections:
    • BinaryBuilder: the tool's features (Toolchains, Sandbox, Audit, Wizard, platforms, languages, tarballs, hints and consistency).
    • Yggdrasil: a new section, "the community build tree for BinaryBuilder recipes", with Community-driven (now "thousands of packages"), JLL packages, Contributing, GPUs, Parallelism and Agents. Its heading has an icon traced from the Yggdrasil logo.
  • Removed cards: Sensible defaults and Experience.
  • Links: feature descriptions link to the matching docs sections.
  • Other pages: the title links home. The demo video, its 630 KB of player code and the buttons only load on the homepage.
  • Accessibility: the feature icons have alt text.

Build

  • Dependencies: Project.toml lists Franklin, NodeJS, BinaryBuilderBase, Downloads and RegistryInstances, with compat bounds. A BinaryBuilderBase 2.0 release can't break the build unannounced.
  • Workflow: the site builds on pushes to master, on pull requests, weekly (so generated pages pick up upstream changes) and on demand.
    • Build job: read-only.
    • Deploy job: a separate job that publishes from master only.
    • Actions: actions/checkout and julia-actions/setup-julia are updated to their current majors.
  • Yggdrasil files: the build downloads platforms/cuda.jl and platforms/mpi.jl from Yggdrasil's master and runs them against BinaryBuilderBase, which avoids installing all of BinaryBuilder.
    • Containment: this code runs only in the read-only build job.
    • Failures: downloads retry, and failures give a clear error. A failed build deploys nothing, so the live site keeps its last good version.
    • Local checkout: set YGGDRASIL_DIR to use one.
    • Not pinned: the files aren't pinned to a commit, so the CUDA and MPI data stays current.
  • Registry: library versions are read with RegistryInstances.jl. The build stops if the General registry is missing, and warns about unregistered packages.
  • Escaping: generated table cells are HTML-escaped unless they're deliberately markup.
  • Site contents: Project.toml, Manifest.toml and the npm files CI creates are kept out of __site.
  • Cleanup: the unused .gitlab-ci.yml and Franklin template assets are removed.

Testing

  • Local build: I ran the exact CI build command locally, including the npm install and prerendering, and checked each generated value in the output.
  • Rendering: I checked the pages in headless Chrome at desktop and narrow widths.
  • Links: every docs anchor and external link resolves.
  • CI: this PR's build runs the new workflow.

🤖 Generated with Claude Code

@ViralBShah ViralBShah changed the title Add auto-generated toolchains page and link landing page to docs Add generated toolchains, GPU and MPI pages; separate Yggdrasil on the homepage Nov 15, 2026
@ViralBShah ViralBShah mentioned this pull request Nov 15, 2026
@ViralBShah ViralBShah changed the title Add generated toolchains, GPU and MPI pages; separate Yggdrasil on the homepage Add generated toolchain, GPU and MPI pages and a Yggdrasil section Nov 15, 2026
@ViralBShah
ViralBShah force-pushed the vs/toolchains-page branch 3 times, most recently from 9807637 to 4e7f991 Compare November 15, 2026 04:40
Pages generated at build time (utils.jl):
- /toolchains/: every GCC, LLVM, Rust, Go and OCaml version, and the
  versions each platform supports, computed from BinaryBuilderBase with
  the same rules as choose_shards and the default LLVM
- /gpus/: CUDA toolkits and their x86_64, ARM server and Jetson builds
  from Yggdrasil's platforms/cuda.jl, and NVIDIA, AMD, Intel, Apple and
  cross-vendor GPU libraries with versions from the General registry
- /mpi/: MPI implementations and the platforms each is built for, from
  Yggdrasil's platforms/mpi.jl
The homepage platform count, toolchain count, OS list and CPU list come
from the same data.

Homepage:
- Fix the unclosed rows="27 attribute that dropped the player's poster
- Split into BinaryBuilder features and a Yggdrasil section, with an
  icon traced from the Yggdrasil logo
- Link features to the relevant documentation
- Load the asciinema player only on the homepage
- Add alt text to the feature icons

Build:
- Project.toml lists Franklin, NodeJS, BinaryBuilderBase, Downloads and
  RegistryInstances, with compat bounds
- Build in a read-only job on pushes, pull requests, weekly and on
  demand; deploy from a separate job only from master
- Update actions/checkout and julia-actions/setup-julia
- Keep Project.toml, Manifest.toml and npm files out of the site
- Remove the unused GitLab CI file and Franklin template assets

Fixes #2

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

Add a table of all the toolchains we have

1 participant