Tools in the footer, and an open-source section on the homepage - #142
Merged
Conversation
Three things, and the first two are gaps the last round left.
/tools had no inbound link anywhere on the site. The footer pointed at one
tool, so the section page I had just rebuilt was reachable only from the
sitemap, and four of the five tools had no sitewide link at all. They now have
a footer group of their own. Five groups do not divide into the footer's four
columns — the fifth was stranded alone on a second row — so the columns flow
into three, and five groups sit three and two.
/tools/vocabulary-test was a 404. Every other tool has an index; that one only
had its language pages, so trimming the URL, or crawling it, hit nothing.
Open source was half a sentence on the homepage ("Open source, no ads.") and
two FAQ answers. It is the thing that makes this different from Tandem and it
is in the header as a star count, so it gets a section: the licence, the fact
that it is the whole app and not a mirror, and that it can be self-hosted.
Every line is checkable in a minute, which is the only kind of claim the
section is allowed to make.
Two deliberate omissions there. It says nothing about tracking or analytics:
the app now ships posthog-react-native and a claim of the kind the rest of the
site makes would be false — see the note going to the owner. And it has no
scroll reveal, though the chapters above it do. Those fade in because what
they hold is a demonstration; this one holds claims, and a claim that depends
on an IntersectionObserver firing is a claim that can fail to appear at all.
Co-Authored-By: Claude Opus 5 <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
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.
Three things. The first two are gaps the last round left.
/toolshad no inbound linkThe footer pointed at one tool, so the section page I had just rebuilt was reachable only from the sitemap — and four of the five tools had no sitewide link at all. They now have a footer group of their own.
Five groups do not divide into the footer's four columns; the fifth was stranded alone on a second row. The columns now flow into three, so five groups sit three and two.
/tools/vocabulary-testwas a 404Every other tool has an index. That one only had its language pages, so trimming the URL — or crawling it — hit nothing. It now lists all 53.
Open source, said out loud
It was half a sentence on the homepage ("Open source, no ads.") and two FAQ answers, for the thing that makes this different from Tandem and that already sits in the header as a star count. It now has a section: BSD-3, the whole app and API rather than a mirror, and self-hostable — each checkable in a minute, which is the only kind of claim it is allowed to make.
Two deliberate omissions. It says nothing about tracking or analytics (see below), and it has no scroll reveal though the chapters above it do — those fade in because they hold a demonstration, and this one holds claims. A claim that depends on an IntersectionObserver firing is a claim that can fail to appear at all.
While checking what the section was allowed to say, I found that the live privacy and cookie policies are now inaccurate.
apps/mobileshipsposthog-react-native ^4.67.0, wired up insrc/lib/analytics.tswith a full event system. The live text says:The session-recording half is still true (
enableSessionReplay: false). The product-analytics half is not. The homepage also says "No ads, no trackers".To be fair to what was actually built: EU Cloud,
disableGeoip: true, identified only by the Better Auth user id, and there is an opt-out in Settings. It is a careful integration. But the policy says the opposite of what ships, and the cookie policy promised to announce the change first.I have not touched the policy text — it is legal wording, and the fix might be to change the app rather than the page. Flagging it rather than deciding it.
npm run lint,npm run check(0 errors) and the build all pass.🤖 Generated with Claude Code