site: correct every use-it surface; plain language throughout - #167
Merged
Merged
Conversation
The /api page advertised the retired interscript.org/api endpoint in its curl hero and generated snippets (404 live; production is api.interscript.org/v1, POST JSON, open CORS) and showed a CDN import of the wrong package name with a strategy that cannot load the ISC-only maps endpoint. The npm card called bare transliterate() with no loader configured. The CLI section used a package and bin name that do not exist (interscript-ts; the bin is interscript) and could not have worked before 5.3.1 anyway - the CLI gained an ISC loader today. The home CTA's curl line fetched a .json the endpoint stopped serving. Every snippet now shows a verified command: the API examples against the live POST endpoint, the CDN/npm cards use the ISC strategy recipe (pinned 5.3.1, probed in a browser), the CLI examples run as shipped, and the new Python card states the one setup step it needs (a maps checkout). /ml adds the no-install paths (REST infer endpoint, the browser demo, the CDN recipe). Headlines rewritten in plain language per the house decision: 'Try it. Copy the snippet. Ship.' -> 'Try the API.', 'Where maps end, models begin' -> 'Neural models for what maps cannot cover', 'Every trap we fell into, now a rule' -> 'How we measure', '580M parameters against the frontier' -> 'Our results against the frontier', 'Measured, or it doesn't ship' -> 'Every number is measured'.
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.
What
A correctness pass over every "how to use us" surface, plus the plain-language headline rewrite.
Corrected (all were wrong against production):
interscript.org/api(404 live) — now the liveapi.interscript.org/v1POST endpointinterscript-ts(a package name that doesn't exist) with anhttpStrategythat cannot load the ISC-only maps endpoint — now the browser-probed ISC recipe, pinned 5.3.1transliterate()with no loader configured (cannot load maps) — now the configure + ISC-strategy forminterscript-ts/ bininterscript-ts— the package and bin areinterscript, and the CLI only gained a working default loader in 5.3.1 (interscript-ts#70).jsonthe maps endpoint stopped serving — now the.iscform it actually servesAdded: /ml now names the no-install paths — the
/v1/inferREST endpoint (open CORS), the browser demo, and the CDN recipe pointer.Plain language: the headlines rewritten per the house decision ("Try the API.", "Neural models for what maps cannot cover", "How we measure.", "Every number is measured.", "Our results against the frontier.").
Verification
Astro build clean. Every snippet on the page was run against the live endpoint or the published package before it went in.