feat(website): add Core Principles tab to landing editor#151
Merged
Conversation
- Add a 6th editor tab ("Core Principles") that swaps the typed-code
view for a grid of twelve keyword tiles (Enjoyable, Type-Safe,
Stateless, Lightweight, SQL, …), each fading in one by one from
top-left to bottom-right
- Rework the hero subtitle ("…persistence layer remains small,
expressive, and fully capable as your application grows")
- Remove the "UTF-8 · Kotlin 2.0" status-bar label from the editor
- Slightly lengthen auto-advance dwell (code scenes ~4.8s; principles
grid ~8s so all tiles are readable)
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.
Summary
Adds a sixth tab to the landing-page hero editor and a couple of copy/UI tweaks (all in
website/src/pages/index.js).6 · principlestab — instead of typed code, the editor renders a 3×4 grid of twelve keyword tiles (keyword + one-line explanation), each fading in one by one, top-left → bottom-right:Wording is accurate to Storm (e.g. No Proxies notes that laziness is explicit via
Ref, since Storm does have lazyRefs and dirty tracking).