Repository navigation
Give each site a calm landing page with a "Why" section - #40
Merged
Merged
Conversation
tala.run, talac.tala.run and tazel.tala.run now each open on a landing page of their own. talac.tala.run and tazel.tala.run used to redirect "/" to their first documentation topic. Every landing page has one headline, two ways in, a "Why Tala?", "Why Talac?" or "Why Tazel?" section of tabs over one code panel, and a short row of next links. The tabs follow the ARIA tabs pattern: arrow keys, Home and End move between them. The code panel stays left to right on the Hebrew pages and has a copy button. Every sample is something that works today. The Tala tabs show HelloWorld and PrimeNumbers, which are copies of Examples/ (a test compares them), a small program that shows an argument evaluated by need, the LLVM IR that talac -O2 made of the gcd loop of Examples/GCD, and a Tazel project file. The Talac tabs show the terminal output of talac 0.6.0 for one command, --emit=metadata, each --emit stage, the optimized IR and a type error. The Tazel tabs show the project file, the everyday commands, target selection, lock graph and a did-you-mean hint. Of the fifteen programs in Examples/, talac 0.6.0 builds four (HelloWorld, GCD, PrimeNumbers, CollatzTrace), so the classes, generators and pattern matching of the others are not shown yet. The old home page said in nearly every paragraph that the work was unfinished, linked "Why Tala?" three times, and numbered its sections. It is gone. The state of the project is said once, as a small badge beside the name in the header. The header no longer repeats a Home link, since the name leads home. On talac and tazel it lists their documentation topics. Styles that only the old home page used are removed. The titles and descriptions of "/" come from the landing content of each site, and the talac and tazel sitemaps list "/". The tests follow: siteHome is "/" everywhere, the tazel canonical path is "/", and the example comparison reads the landing samples.
Contributor
Author
|
Self-review: read the whole diff. |
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.
Each of tala.run, talac.tala.run and tazel.tala.run opens on its own landing page (talac/tazel no longer redirect
/to a docs topic). The page has a headline, two buttons, a tabbed Why Tala? / Why Talac? / Why Tazel? section modelled on kotlinlang.org, and a short next-links row.Calmer: the old home page repeated a work-in-progress disclaimer in nearly every paragraph, linked "Why Tala?" three times, and numbered its sections. The project state is now said once, as a small header badge. The header drops the redundant Home link; on talac/tazel it lists their docs topics. Styles used only by the old home page are removed.
Every sample works today. Tala tabs: HelloWorld and PrimeNumbers (copies of
Examples/, compared by a test), a small call-by-need program (prints 42, never divides by zero), the-O2LLVM IR of the gcd loop, and a Tazel project file. Talac tabs: realtalac 0.6.0terminal output for building,--emit=metadata, each--emitstage, optimized IR, and a type error. Talac 0.6.0 builds 4 of the 15 programs inExamples/, so classes, generators and pattern matching are not shown yet.Tabs follow the ARIA tabs pattern (arrows, Home, End). The code panel stays LTR on the Hebrew pages and has a copy button.
Testing:
npm run check,format:check,test(44),build. Checked in the browser pane at 1280×800 and 375×812, in dark and light themes, in English and Hebrew: no horizontal overflow and no console errors. Not merged until the design is approved.