Repository navigation
Conversation
Preserve space-1 and the production documentation default, add the SDK variant section, remove the v2-only root fallback, and guard the exported mapping in tests.
No content changes. Test preview generation after GitBook posted new site-wide preview statuses on the previous head rather than the merge head.
Keep README.md and SUMMARY.md at the repository root instead of the old v2-only fallback. Guard the neutral root configuration and homepage in tests.
10 of 12 tasks
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.
Summary
Preview the full generated Node, Browser, React and Vue SDK documentation with native GitBook v1/v2 variants. SDK READMEs and source comments in reflagcom/javascript remain authoritative; these are deterministic generated copies, not separately maintained SDK prose.
Mapping update after the real site export
mainat38f10c754fe5055639f68c134c2e391344777cacwith a normal merge. All exported production content/navigation/assets match that main commit.space-1, including title,reflag-docspath, default status and repository-root (/) content directory.javascript-sdks, withsdk-preview-v2andsdk-preview-v1mapped to the complete generated variant directories. V2 is the default only within the SDK section..gitbook.yamlfallback with explicit neutral defaults:root: ./,structure.readme: README.md,structure.summary: SUMMARY.md. Removing the config entirely produced 404s in a GitBook revision; the explicit root config restores the real homepage/navigation.Sources and generated content
b4fe5b3d9386b87c6546175c323862d9878e1430; Node 1.8.3, Browser/React 1.7.4, Vue 1.5.7. Browser/React/Vue package trees match published-tag commit70b7fbe7e65e95e7bce5ccad64400b0c3e06f63c.9f3a0ae027e386747a2d4cf7683a68dcab70b355; all four packages 2.0.0-next.0. This is unreleased source documentation, not a package release or packed/deployed acceptance.Validation
GitBook preview / publication boundary
Working current-head content preview — browser-verified Getting started, React SDK and its API reference; the homepage/sidebar now render without 404s. GitBook statuses are successful on
e47acbe1c12be4627cf03607da65f5065767f16b.The native selector is still not activated/verified. This restored preview renders existing
space-1content and the existing site's navigation, not the proposed new SDK section/variants. It is not evidence that PR previews apply site-wide structure changes. Earlier v2-only and brokenQKL5NIcHVQZMxg8rYJEvrevisions are superseded.No site was created, no live GitBook connection/default/sync direction was changed, and this PR is not merged or published. Do not switch the live connection to this branch or merge to main just to obtain a preview. Existing route/identity acceptance and mobile/full SDK switching remain gates.
The six local shared-v2 guide edits are excluded. The automatic release-scoped publisher remains a separate unfinished JavaScript-repository task and must preserve SDK-source ownership, published package/major boundaries and archives. Shared-v2 migration, compatible released SDK/CLI artifacts and server/snapshot readiness still gate production cutover.