feat: rewrite the get started page - #213
Merged
Merged
Conversation
The page was one paragraph and a screenshot, which left a visitor unable to
tell what Flix needs, what it looks like, or what to do next. It now walks the
three routes in order of how much they ask of you: the playground, the Visual
Studio Code extension, and the command line.
The install animation keeps its place but gains a caption saying what it
shows, real alt text, and the two facts it cannot: that Java 21 is required
and where the extension lives on the Marketplace. Homebrew, Nix, and the JAR
each get the one command that fetches Flix, with flix init and flix run
spelled out beneath them.
The first program is new. The book's getting-started chapter carries the
install steps but no code, so nothing on either site showed what a Flix
program looks like at the moment someone is deciding whether to keep reading.
It is the front page's httpExample cut down to a single request, chosen
because the effect is the point: fetching a URL is visible in the signature as
\ { Http, IO }. Verified against Flix 0.75.1, where it prints Status: 200.
The page ends by handing off to the book, to its install chapter for Neovim,
Emacs, and the JAR workflow, and to Zulip.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <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
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.
Why
/get-started/was one paragraph and a screenshot. It never said what Flix requires, never showed a line of Flix, and ended without a next step — on the page a visitor lands on when they have decided to try the language.What
Four sections, ordered by how much each asks of the reader:
flix init/flix runspelled out beneath.The program
The book's getting-started chapter has the install steps but no code, so nothing on either site showed what Flix looks like at the point someone is deciding whether to keep reading. This is the front page's
httpExamplecut down to a single request — the middleware stack, headers, retry and circuit breaker removed — because the effect is the point: reaching the network is visible in the signature.Testing
Status: 200. The version tested was extracted from the built HTML, not the source, so what ships is what ran.The Flix Programming Language 0.75.2.brew info flixconfirms the formula is in homebrew-core. The Nix command comes from the book; there is no nix on the machine this was written on, so it is unverified.npm run buildpasses, and the page was swept for the whitespace-stripping bug fixed in fix: restore spaces lost between inline elements #212.Notes
.btn-success. Bootstrap compiles button variants with literal colours, so it renders Bootstrap's#198754rather than the site green — the.btn-successoverride that fixes this is deliberately not in this PR, which is page-only. Worth a follow-up, along with.btn-primary, which is Bootstrap blue on this site for the same reason.play.flix.devpermits outbound requests is unverified.🤖 Generated with Claude Code