Repository navigation
feat(landing): MCP and the studio, animated, and their docs - #14
Merged
Merged
Conversation
…tect and what is open in production
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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 new sections on the landing page, after the contract section:
#mcp): a scripted chat in a terminal window. A user asks, the model callsgetTeasByIdwith"sencha"and gets the 400 the contract wrote (params.id: expected an integer). It callsgetTeasinstead, gets a 200, and answers. Bubbles spring in, the status stamps pop, typing dots show between steps, and the chat loops while it is on screen. Next to it: the one-linemcp: trueand three facts.#studio, "coming in 0.11"): a studio window that runs by itself. Live rows slide in with a flash, the KPI sparklines draw and move, route p95 bars grow, the path map unfolds, and job bars fill and turn green. The tabs advance every 4.2 s with a progress line. A click holds a tab.Both run only while visible. They follow
prefers-reduced-motion, so a reduced-motion visitor gets the final state with no loop. Each has its own background tone (data-tone). On phone width nothing overflows: 375 px wide, scrollWidth 375.Docs:
/docs/studio: tabs,protect, JSON/docs/api/app: theinspector,protectandmcprows/docs/deploy: a new "What is open in production" section with a table of/docs,/openapi.json,/_inkanand/mcp, saying how to close each one or guard itDepends on inkanjs/inkan#43 for the studio and
protect. The pages say "0.11", so merge after that release. Typecheck and lint are clean, checked innext devat desktop and mobile width.