docs(roadmap): plan Studio's ocppdebugkit.com coverage as an S6 deliverable#46
Merged
Conversation
…erable Record the S6 website deliverable: a /studio section on ocppdebugkit.com (positioning, the library-vs-instrument split with the toolkit, feature highlights, screenshots, download links) with cross-links from the toolkit landing and inspector, using the conformance contract as the trust hook. Capture the repo-structure decision: the site stays in the toolkit monorepo (apps/web) rather than a separate website repo, because its live inspector already depends on the toolkit's workspace packages and Studio coverage is static content. It is a cross-repo deliverable, so the page and its issues are filed in the toolkit repo. Rename the S6 theme to "1.0 polish & launch".
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
Records the S6 website deliverable in the roadmap: Studio's coverage on
ocppdebugkit.com.
Why
The ecosystem site should cover Studio at 1.0. This captures the plan and the
repo-structure decision now, so it isn't lost before S6 starts.
Decision captured
/studiopage on ocppdebugkit.com: positioning, thelibrary-vs-instrument split with the toolkit, feature highlights, screenshots,
and download links, plus cross-links from the toolkit landing and inspector.
The conformance contract (two independent implementations, one trace format)
is the trust hook.
apps/web), not aseparate
websiterepo. The site's live inspector already depends on thetoolkit's workspace packages, and Studio coverage is static content; a separate
repo would add npm version-lag for no present benefit. Revisit only if the site
later needs an independent brand or deploy cadence.
starts; this repo's roadmap references it as an S6 deliverable.
Scope
Docs only —
ROADMAP.md(expanded S6 section + theme renamed to"1.0 polish & launch"). No engine/UI/CLI change.