docs: add live-data-products concept page#36761
Conversation
|
I think @kay-kim had a POV here that I agree with - we should make this some of this content the front page for the docs. So our "What is Materialize" page of the docs would look like this:
Next, I wouldn't put this in the "concepts" section. Rather, I'd add a new section for "Architecture Patterns". And then let's use most of the content from this page, but call it the "Live Context Graph"
@sjwiesman, @kay-kim lmk if you agree! IMHO let's make these changes, and let's ship it. I can think of a few ways to make this even better, but let's not let perfection be our enemy! |
|
I can make a few of the changes and push an update - give me a few mins! |
|
@sjwiesman / @kay-kim lmk how you feel about this structure! |
|
Structure looks good but there are merge conflicts in your commit 😄 |
|
I am bad at git |
kay-kim
left a comment
kay-kim
left a comment
There was a problem hiding this comment.
Heh heh ... so, I'll make some updates on Friday per slack discussion.
|
I need to git good. Let me get rid of some of these changes and clean it up, sorry! |
|
Actually, will have to be next week. |
|
Oh ... lol .. I misunderstood what was being reverted. I thought everything was being reverted. I'll:
|
Introduce /concepts/live-data-products/ — a new front-door concept page that teaches Materialize's primary use case: building the nouns of your business as live SQL views that compose into your business's ontology. The page opens with the silo-stitching problem (one entity scattered across CRM, OMS, billing, support, fulfillment), shows how a single view stitches them, and walks through composition (Customer → Order → Store → at_risk_orders). It names strict serializability inline as the consistency model and "about a second" as the freshness claim. The closing sections frame the agentic feedback loop (observe → think → act → observe the consequences) and the ontology as the unit of work Materialize is designed for. Wire the page into navigation: - Add as the second row in the Concepts table (after Reaction Time). - Add as the first bullet in get-started/_index.md "Learn more". - Add a "## Start here" section on the docs home page. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-authored-by: Seth Wiesman <sjwiesman@gmail.com>
|
Retriggered the infra-affected tests |
4 participants
Motivation
Materialize's user docs don't currently teach the primary use case in declarative, solution-first terms: that you build the nouns of your business as live SQL views, and together they form your business's ontology. New developers (especially AI/agent platform builders) have to assemble this picture themselves from the mechanical concept pages (Clusters, Sources, Views, Indexes, Sinks). This PR adds a front-door concept page that opens with the worldview and shows it through a worked example.
Description
Adds
/concepts/live-data-products/and wires it into three navigation surfaces:doc/user/content/concepts/_index.md, positioned second (after Reaction Time).doc/user/content/get-started/_index.md.doc/user/content/_index.md), inserted between the headless intro include and the "What's new!" callout.The page is audience-broad (developers + AI/agent platform builders), agent-forward in §5 but not agent-only elsewhere. It opens with the silo-stitching problem (Customer scattered across CRM/OMS/billing/support/fulfillment), shows a single view that stitches the silos, then walks through composition (Customer → Orders → Stores →
at_risk_orders). §4 names strict serializability inline and states that a change propagates through the entire business within about a second. §5 frames the agentic feedback loop (observe → think → act → observe the consequences) and gives agent builders two named primitives (Read, Compose) plus a link to the MCP integration. §6 closes with the reframe that a live data product is the unit of work Materialize is designed for.Verification