docs: surface the 1.52.0 feature wave on discovery + positioning pages#934
Merged
Conversation
Adds the engine 1.52.0 wave to the top-of-funnel and positioning docs (it was absent from all of them after shipping post-overhaul): - ROCKY_EXPLAINED.md: feature-at-a-glance rows, command-table entries, and prose sections for config groups (+enforce), named/declarative + fixture unit tests, model [tags], per-column docs (catalog JSON), and rocky emit-sql. - comparison.md: Data Quality rows (unit tests, named/generic tests) + a Modeling utilities row (surrogate keys) + a no-lock-in emit-sql line; competitor cells marked '(verify against current vendor docs)'. - README.md: a no-lock-in bullet + the dbt-parity wave in the feature list. - governance.md: enforced config groups + model-tags sections (distinct from UC tags). - introduction.md / roadmap.md / index.mdx / no-lock-in.md: wave mentions + links. Grounded against shipped source; dbt qualified, no overclaims, SQL stays first-class.
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.
PR 2 of the docs sweep (follows #930, which covered reference/concepts/dagster). This puts the engine 1.52.0 wave on the top-of-funnel and positioning pages, where it was completely absent after shipping post-overhaul.
Pages
ROCKY_EXPLAINED.md— feature-at-a-glance rows, Quick-Reference + command-map entries, and short prose sections for config groups (+enforce), declarative named tests + fixture unit tests, model[tags], per-column docs (catalog JSON), androcky emit-sql.getting-started/comparison.md— Data Quality rows (unit tests, named/generic tests) + a Modeling-utilities row (surrogate keys) + a no-lock-inemit-sqlline. Only Rocky's cells are asserted (grounded in 1.52.0 commits); competitor cells are marked(verify against current vendor docs), not filled from memory.README.md— a no-lock-in bullet + the dbt-parity wave in the feature list.guides/governance.md— enforced config groups + model-tags sections (kept distinct from the existing Unity Catalog[governance.tags]section).introduction.md/roadmap.md/index.mdx/no-lock-in.md— wave mentions, the "Shipped" list, a landing card, and the surrogate-key cross-link fixed to the newmodel-format.md#surrogate_keyanchor.Positioning + accuracy
Authored under Rocky's positioning rules (qualify "dbt Core/Fusion", lead with the typed-graph/compile-time-enforcement framing, no cross-team-contracts/branch/replay/CLL overclaims, SQL stays first-class, dbt+SQLMesh only). The adversarial verify pass caught and removed one from-memory competitor claim ("dbt Core 1.8 ships unit tests"). Every Rocky claim is grounded against shipped source.
Reconciled with #933
#933(the source-verified compiler-stage fix toROCKY_EXPLAINED.md) merged after this branch forked, so I rebased onto post-#933 main. Verified the result keeps #933's 9-stage correction and does not reintroduce "breaking-change classification" as a compiler stage; my additions are feature sections, orthogonal to the stage content. A stray code-fence the drafter added was removed (fences balanced).Verification
astro buildgreen (89 pages, no errors/broken links).gold-tier values).🤖 Generated with Claude Code