docs: add the data family (orm + schema + adapters) [#72, HOLD until publish + #66]#73
Closed
suleimansh wants to merge 1 commit into
Closed
docs: add the data family (orm + schema + adapters) [#72, HOLD until publish + #66]#73suleimansh wants to merge 1 commit into
suleimansh wants to merge 1 commit into
Conversation
…s site Child #72 of the data-layer graduation (#64). Sweeps every package-list surface to include the four new packages now on main: - README.md package table + "how they fit together" diagram - docs/packages/index.md (+ a "two engine families" section) - docs/guide/index.md - docs/.vitepress/config.ts sidebar (new "data family" group) - Architecture.md: candidates -> graduated (Phase 0, pending #66) - new docs/packages/orm.md + docs/packages/schema.md schema is documented as preview/experimental (its API is still a spike). vitepress docs:build passes (links + anchors resolve). DO NOT MERGE until: (1) the @gemstack naming is confirmed with the Vike team (#66), and (2) the packages are published to npm (#67/#68) so the version badges and install lines are real. The docs site auto-deploys on merge to main, so merging early would advertise unpublished packages under a provisional name.
This was referenced Jun 27, 2026
Member
Author
|
Closing per #66 (closed): the data layer stays @universal-orm and will NOT be presented as GemStack packages, so this docs PR is moot rather than something to rework. The engine packages themselves are being removed from this repo (see the removal PR) since vike-data / @universal-orm is the single source of truth. |
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.
Closes #72 (when merged). Part of the data-layer graduation epic #64.
Sweeps every package-list surface to include the four new packages now on
main(orm,schema,orm-memory,orm-drizzle):docs/packages/orm.md+docs/packages/schema.mdschemais documented as preview / experimental (its API is still a spike and the compilers emit representative output).vitepress docs:buildpasses — links and the#adaptersanchor resolve.The docs site auto-deploys on merge to
main, so this must not land until both are true:@gemstacknaming (vs keeping@universal-ormparallel). The names in these docs are provisional until then.private/unpublished today, so the npm version badges andnpm install @gemstack/...lines would 404 if this went live now.Merging early would advertise unpublished packages under a name not yet agreed. Ready to flip the moment both clear.