Repository navigation
Use the brand tagline on the welcome screen - #42
Merged
Merged
Conversation
"Design, simulate, and build circuits beautifully." is the kind of
adjective the brand guide asks copy to do without ("show the thing
happening instead of using adjectives"). The welcome screen now says
the brand kit's tagline, "Wire it. Run it. See it work.", which is
already on the LinkedIn cover and the launch page.
Not the handbook's recommended "The AI writes the circuit. The bench
runs it.": the web build has no assistant for now, so it would promise
the welcome screen something it doesn't have. The tagline decision
itself (D12) stays open.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
burhankhanzada
added a commit
that referenced
this pull request
Oct 4, 2026
**Merge after #42 (tagline) and #43 (brand fonts):** this changelog describes both. v0.1.1 was drafted but never published, so **0.1.2 is the first release anyone installs**. - `pubspec.yaml` → `0.1.2+102` (the release workflow's major·10000 + minor·100 + patch). It's also the version the web app reports, and the Release Notes tab shows that version's changelog section. - `CHANGELOG.md`: `[Unreleased]` becomes **`[0.1.2] - 2026-10-04`**, adding what merged since v0.1.1 in the user's words: - **Added:** the Pico W (it was missing), mouse pan, ⌘/ comments, release notes, the macOS Window menu. - **Changed:** the brand look and type, the simpler welcome screen, the empty editor, no sign-in UI where there is no sign-in. - **Fixed:** a new project starts clean, sketch colouring, Help ▸ Welcome, ⌘W, pane edges. - Cloud projects are now described as in the hosted *desktop* builds, since the web app leaves accounts out (pro#4). - No Arduino trademark in the new lines. - `release_notes_test.dart` now asks for `pubspec.yaml`'s version and requires its own section, so a version bump without one fails. It used to ask for `0.0.0` and fall back to `[Unreleased]`. Checked: bumping to 0.1.3 without a section fails with *CHANGELOG.md needs a "## [0.1.3] - <date>" section*. **After this merges:** tag `v0.1.2` on `main` to build and draft the release for all three platforms, then publish the draft. The unpublished v0.1.1 draft can be deleted. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.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.
The welcome screen's subtitle was "Design, simulate, and build circuits beautifully.", the kind of adjective the brand guide asks copy to avoid (show the thing happening instead of using adjectives). It now says the brand kit's tagline, "Wire it. Run it. See it work.", already on the LinkedIn cover and the launch page.
Not the handbook's recommended "The AI writes the circuit. The bench runs it.": the web build has no assistant for now (pro#4), so the welcome screen would promise something it doesn't have. The tagline decision (handbook D12) stays open; this is a one-line string to change if you pick another.
🤖 Generated with Claude Code