Repository navigation
landing: adopt go-fft's layout, keep go-ndarray's content and logo - #10
Merged
Merged
Conversation
Replace the old nav/hero/sections layout with the go-* family template go-fft.github.io uses: a sticky header, a two-column hero with a code terminal, the repository strip, a "Why" card grid, a stats panel, the repository cards and the CTA band. partials/styles.html and partials/theme-toggle.html are verbatim copies of go-fft's, and the emerald [params.brand] block is go-fft's, unchanged. The content is the landing's own (fact-checked in #9) plus the README of go-ndarray/ndarray at v0.2.2: the terminal shows lines of its Example section verbatim, the stats panel cites the README's Zen 3 / NumPy 2.5.3 figures, and the wins-and-losses paragraph is kept in full. The GitHub button keeps the Octicons mark-github icon. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Restyles the landing page on the go-* family template that go-fft.github.io uses, so the two emerald scientific-computing orgs read as one family.
Taken from go-fft: sticky header (logo, Why / Repos / Quality / Docs, the System / Light / Dark toggle, a GitHub button), a two-column hero with a code terminal, the repository strip, the "Why" eyebrow + card grid, the dark stats panel, the "What is here." repository cards and the gradient CTA band, plus the footer.
partials/styles.htmlandpartials/theme-toggle.htmlare byte-identical copies of go-fft's, and[params.brand]is go-fft's emerald block, unchanged.Kept from go-ndarray: its logo and favicon, its links (docs,
go-ndarray/ndarray, brand), and the Octiconsmark-githubicon on the GitHub button (#8).Content: only the landing's existing text (fact-checked in #9) and the README of
go-ndarray/ndarrayat v0.2.2:Workspace, SIMD on amd64/arm64, accurateExp/Log, multi-arch CI, the cgo-free ndarray that was missing, BSD-3-Clause);MatMulagainst single-threaded OpenBLAS, ≤ 0.51 ULP), and under it the full wins-and-losses paragraph, including where it is slower;ndarrayrepository card is taggedv0.2.2; the CTA band links to the docs' performance page.Left out because go-ndarray has no equivalent: go-fft's statistic for "rows at or above numpy" and its comparison against FFTW. No new figures were added.
Verified locally with Hugo 0.135.0 (the version CI pins): both sites render the same element skeleton, no
ZgotmplZ, and there is no horizontal overflow at a 390 px phone width. I checked the result in both light and dark themes.🤖 Generated with Claude Code