Add a website badge and a walkthrough video to the README - #301
Merged
Conversation
amaudruz
marked this pull request as ready for review
August 26, 2026 09:19
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.
Two commits.
CHOO-2351
Website badge. Links to https://www.flintai.dev/products/switch, first in the row and ahead of the license. Everything else there — license, docs, contributing, Discord — assumes you have already decided to use Switch; someone who has just landed and wants to know what it is had nowhere to go.
Watch it work, immediately before "Why Switch". An incident in Discord: someone reports checkout failing, an agent opens an incident channel, pulls the error rate and finds the deploy behind it, with a second agent doing the charting. One collapsible block per app, Discord open and Slack and Mattermost waiting, so adding the next recording is pasting one URL.
How the video is hosted, and why it matters
The recording is a GitHub attachment, not a file in this repository. Nothing was committed.
That was worth establishing rather than assuming, because most of the obvious ways do not work. Checked against the rendered page on a branch, not from memory:
<video>tag.mp4committed hereblob/…?raw=trueuser-attachmentsURL on its own lineIt also plays inside
<details>and inside a centered<div>, which is what lets the section hold one block per app without running long.The earlier revision of this branch committed an 11 MB
.mp4and a poster image. Both are gone, and the branch was rewritten so the blobs are not in its history — three recordings would otherwise have put roughly 33 MB into the repository permanently, paid by everyone who clones. A comment above the section says so, so the next person reaches for an attachment instead.Worth a look before merging