Repository navigation
Rebuild the Warehouse page on the product page template - #21397
Conversation
Move /context-warehouse/warehouse to ProductReaderView with the same sections as other product pages. The warehouse is a sales-led beta, so the hero and closing section send people to sales instead of signup. Copy is aligned with the warehouse docs, and the feature comparison is checked against BigQuery, Snowflake, and Redshift docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9JmPnzu6DFbzWDyi53Vxo
Deploy preview
Changed pages
|
There was a problem hiding this comment.
PostHog Review · Standard · reviewed 573ba16: 1 Should fix.
This is the only automatic review while this pull request is a draft. Comment @posthog review to review new changes sooner. Otherwise, a review of the new changes runs when you mark it ready for review.
| ai: { | ||
| intro: 'Ask PostHog AI any question you want about your data.', | ||
| copyPrompts: true, | ||
| groups: [ |
There was a problem hiding this comment.
P2 · Populate the warehouse MCP tool categories
On the warehouse page, selecting the MCP tools tab always displays “No tools match your search,” even with an empty search. AskAnything builds its tool list from ai.mcpFeatures, but this new configuration omits that field, so it returns no tools regardless of the catalog contents. Populate the relevant feature categories or hide the tools tab.
Bundle reportTotal JS (gzip)10.39 MiB (-0.9 KiB / -0.0%) Largest changed named chunks
Eager graph (modules shipped in each entrypoint's initial chunks)
Largest modules in the
|
| Module | Size |
|---|---|
./src/data/mcp-tools.json |
1423.2 KiB |
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css |
825.0 KiB |
./src/components/Stickers/Stickers.tsx |
696.4 KiB |
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js |
481.4 KiB |
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/x-ray.mjs |
481.2 KiB |
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/trenchcoat.mjs |
450.8 KiB |
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules |
395.1 KiB |
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/im-the-driver.mjs |
385.8 KiB |
./src/hooks/useCustomers.tsx + 59 modules |
380.8 KiB |
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/tourist.mjs |
364.6 KiB |
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js |
354.8 KiB |
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules |
351.4 KiB |
./src/components/ProductComparisonTable/index.tsx + 130 modules |
311.4 KiB |
./node_modules/.pnpm/framer-motion@14.0.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/framer-motion/dist/es/render/components/motion/proxy.mjs + 127 modules |
287.8 KiB |
./node_modules/.pnpm/@posthog+brand@0.13.0_react@18.3.1/node_modules/@posthog/brand/dist/generated/hoggies/svg/doll-house.mjs |
284.1 KiB |
Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).
…products menu - Move src/pages/context-warehouse/warehouse.tsx to src/pages/warehouse.tsx - Redirect /context-warehouse/warehouse to /warehouse - Point existing links and redirects at /warehouse - Add Warehouse after Tracing in the products menu Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Vale prose linter → found 8 errors, 168 warnings, 9 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 29:36 | warning | Use 'TL;DR' instead of 'tl;dr'. | Vale.Terms |
| 29:241 | warning | 'embeddable' is a possible misspelling. | PostHogBase.Spelling |
| 31:4 | warning | 'DuckDB has two modes' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 43:318 | warning | 'parallelization' is a possible misspelling. | PostHogBase.Spelling |
| 47:4 | warning | 'DuckDB is lightweight' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 53:90 | warning | 'toolset' is a possible misspelling. | PostHogBase.Spelling |
| 55:4 | warning | 'Notable ClickHouse and DuckDB libraries' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 57:85 | warning | Use 'ClickHouse' instead of 'clickhouse'. | Vale.Terms |
| 59:5 | warning | 'What is clickhouse-local?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 59:13 | warning | Use 'ClickHouse' instead of 'clickhouse'. | Vale.Terms |
| 63:2 | warning | Use 'ClickHouse' instead of 'clickhouse'. | Vale.Terms |
| 63:273 | warning | 'benchmarked' is a possible misspelling. | PostHogBase.Spelling |
| 65:40 | warning | Use 'ClickHouse' instead of 'clickhouse'. | Vale.Terms |
| 67:5 | warning | 'What is DuckLake?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 71:4 | warning | 'Infrastructure match-up: scaling ClickHouse versus DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 87:4 | warning | 'Interface match-up: connecting to ClickHouse versus DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 91:132 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 93:179 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 101:4 | warning | 'Performance match-up: measuring ClickHouse and DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 105:289 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 105:402 | warning | 'hoc' is a possible misspelling. | PostHogBase.Spelling |
| 107:4 | warning | 'Type match-up: how ClickHouse and DuckDB structure data' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 113:4 | warning | 'How we use ClickHouse and DuckDB (and Postgres)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 119:8 | warning | 'architected' is a possible misspelling. | PostHogBase.Spelling |
| 119:31 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 119:364 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 123:26 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 123:298 | warning | 'Tada' is a possible misspelling. | PostHogBase.Spelling |
| 127:1 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 127:98 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 127:208 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 129:69 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
contents/blog/duckdb-vs-postgres.mdx — 0 errors, 18 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 72:440 | warning | 'columnstore' is a possible misspelling. | PostHogBase.Spelling |
| 88:153 | warning | 'safekeeps' is a possible misspelling. | PostHogBase.Spelling |
| 132:641 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 136:5 | warning | 'Communicating with Postgres (and why we built Duckgres)' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 136:51 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 138:104 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 140:253 | warning | 'facto' is a possible misspelling. | PostHogBase.Spelling |
| 140:335 | warning | 'psql' is a possible misspelling. | PostHogBase.Spelling |
| 140:366 | warning | 'pgAdmin' is a possible misspelling. | PostHogBase.Spelling |
| 142:40 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 142:145 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 142:485 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 142:549 | warning | 'lakehouse' is a possible misspelling. | PostHogBase.Spelling |
| 142:703 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
| 160:233 | warning | 'pooler' is a possible misspelling. | PostHogBase.Spelling |
| 162:92 | warning | 'Citus' is a possible misspelling. | PostHogBase.Spelling |
| 180:73 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 180:439 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
contents/blog/duckdb-vs-sqlite.mdx — 0 errors, 18 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 11:53 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 11:86 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 41:4 | warning | 'What is DuckDB?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 45:387 | warning | 'colocated' is a possible misspelling. | PostHogBase.Spelling |
| 47:370 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 51:4 | warning | 'Architecture matchup: SQLite vs DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 53:61 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 59:83 | warning | 'pushdown' is a possible misspelling. | PostHogBase.Spelling |
| 61:4 | warning | 'Performance matchup: SQLite vs DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 69:29 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 71:4 | warning | 'Concurrency performance: SQLite vs DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 79:4 | warning | 'SQLite vs DuckDB placement within their niches' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 81:119 | warning | 'smidge' is a possible misspelling. | PostHogBase.Spelling |
| 83:606 | warning | 'networkless' is a possible misspelling. | PostHogBase.Spelling |
| 89:4 | warning | 'So is DuckDB really the SQLite of OLAP?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 95:60 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 95:166 | warning | 'lakehouse' is a possible misspelling. | PostHogBase.Spelling |
| 95:207 | warning | 'Duckgres' is a possible misspelling. | PostHogBase.Spelling |
contents/blog/what-is-a-context-warehouse.md — 0 errors, 20 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 25:90 | warning | Use the Oxford comma before 'and' or 'or' in a list of three or more items. | PostHogBase.OxfordComma |
| 27:40 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 31:4 | warning | 'Why "data warehouse" stopped being the right word' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 31:9 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 33:3 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 37:39 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 39:4 | warning | 'Data warehouse vs. context warehouse' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 39:4 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'Data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 46:52 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 73:197 | warning | Use 'enables you to' instead of 'allows you to' when describing what PostHog does. | PostHogEditorial.EnableNotAllow |
| 82:179 | warning | 'else's' is a possible misspelling. | PostHogBase.Spelling |
| 84:63 | warning | 'psql' is a possible misspelling. | PostHogBase.Spelling |
| 85:120 | warning | 'polars' is a possible misspelling. | PostHogBase.Spelling |
| 93:58 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 110:4 | warning | 'FAQ' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 112:45 | warning | 'lakehouse' is a possible misspelling. | PostHogBase.Spelling |
| 114:7 | warning | 'lakehouse' is a possible misspelling. | PostHogBase.Spelling |
| 116:53 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 118:133 | warning | Capitalize 'Experiments' for PostHog's product. Use 'experiments' for the general industry concept. | PostHogBase.ProductNames |
| 120:36 | warning | Use 'FiveTran' instead of 'Fivetran'. | Vale.Terms |
contents/blog/why-we-rebuilt-our-data-warehouse.md — 1 errors, 13 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:27 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 23:20 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 38:26 | warning | 'multitenant' is a possible misspelling. | PostHogBase.Spelling |
| 38:50 | warning | Use 'ClickHouse' instead of 'Clickhouse'. | Vale.Terms |
| 55:86 | warning | Use 'ClickHouse' instead of 'Clickhouse'. | Vale.Terms |
| 63:283 | warning | Use 'ClickHouse' instead of 'Clickhouse'. | Vale.Terms |
| 63:338 | warning | 'multitenancy' is a possible misspelling. | PostHogBase.Spelling |
| 67:4 | warning | 'We've rebuilt on top of DuckDB' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 76:162 | warning | 'polars' is a possible misspelling. | PostHogBase.Spelling |
| 77:136 | warning | 'whatever's' is a possible misspelling. | PostHogBase.Spelling |
| 89:5 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 91:65 | warning | Use American English. Use 'behavior' instead of 'behaviour'. | PostHogBase.AmericanEnglish |
| 93:383 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
| 95:21 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
contents/blog/why-you-should-use-a-data-warehouse.md — 2 errors, 21 warnings, 3 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 3:30 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 16:22 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 22:21 | suggestion | Avoid hedging. Be opinionated instead of saying 'it depends'. | PostHogEditorial.Hedging |
| 22:291 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 26:4 | warning | 'Why you shouldn’t use a data warehouse, according to our own data engineers' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 26:28 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 28:5 | warning | Use 'TL;DR' instead of 'tl;dr'. | Vale.Terms |
| 28:16 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 32:60 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 32:82 | warning | 'Estefania' is a possible misspelling. | PostHogBase.Spelling |
| 32:223 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 34:128 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 40:12 | warning | 'Estefania' is a possible misspelling. | PostHogBase.Spelling |
| 46:5 | warning | '3. “All your needs are already met” / “Money”' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 58:113 | suggestion | Prefer 'proper nouns or they' over 'he'. | PostHogBase.Inclusivity |
| 58:187 | suggestion | Prefer 'proper nouns or their/theirs' over 'His'. | PostHogBase.Inclusivity |
| 64:96 | warning | Use American English. Use 'judgment' instead of 'judgement'. | PostHogBase.AmericanEnglish |
| 64:171 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 66:4 | warning | 'Why you should use a data warehouse' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 66:25 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 68:5 | warning | Use 'TL;DR' instead of 'tl;dr'. | Vale.Terms |
| 68:236 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 72:62 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 82:8 | error | 'something' is repeated! | Vale.Repetition |
| 90:198 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 92:171 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
contents/customers/qubs.md — 3 errors, 30 warnings, 6 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:12 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 9:75 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 11:28 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 11:186 | warning | 'Qubs's' is a possible misspelling. | PostHogBase.Spelling |
| 11:219 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 15:1 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 26:1 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 28:93 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 30:55 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 30:330 | warning | 'Gheorge' is a possible misspelling. | PostHogBase.Spelling |
| 35:8 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 35:33 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 41:284 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 41:342 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 41:351 | warning | 'Qubs's' is a possible misspelling. | PostHogBase.Spelling |
| 45:52 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 45:96 | warning | Capitalize 'Endpoints' for PostHog's product. Use 'endpoints' for the general industry concept. | PostHogBase.ProductNames |
| 45:156 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 45:324 | suggestion | Prefer 'proper nouns or them' over 'him'. | PostHogBase.Inclusivity |
| 45:389 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 45:446 | suggestion | Prefer 'proper nouns or they' over 'he'. | PostHogBase.Inclusivity |
| 49:180 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 54:6 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 54:75 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 56:1 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 56:30 | suggestion | Prefer 'proper nouns or they' over 'he'. | PostHogBase.Inclusivity |
| 56:208 | suggestion | Prefer 'proper nouns or their/theirs' over 'his'. | PostHogBase.Inclusivity |
| 58:127 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 58:152 | suggestion | Prefer 'proper nouns or them' over 'him'. | PostHogBase.Inclusivity |
| 64:1 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 66:99 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 66:163 | suggestion | Prefer 'proper nouns or their/theirs' over 'his'. | PostHogBase.Inclusivity |
| 66:231 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 68:88 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 72:45 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
| 74:5 | warning | 'Gheorghe' is a possible misspelling. | PostHogBase.Spelling |
| 74:92 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 74:111 | warning | Capitalize 'Error Tracking' for PostHog's product. Use 'error tracking' for the general industry concept. | PostHogBase.ProductNames |
| 74:140 | warning | 'Qubs' is a possible misspelling. | PostHogBase.Spelling |
contents/docs/data-warehouse/warehouse/connect.mdx — 0 errors, 9 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 15:42 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 15:96 | warning | 'Trino's' is a possible misspelling. | PostHogBase.Spelling |
| 15:206 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 29:84 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 35:30 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 35:208 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 81:23 | warning | 'Trino's' is a possible misspelling. | PostHogBase.Spelling |
| 89:128 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 102:78 | warning | 'allowlisting' is a possible misspelling. | PostHogBase.Spelling |
contents/docs/data-warehouse/warehouse/index.mdx — 0 errors, 5 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 17:80 | warning | Capitalize 'Data Warehouse' for PostHog's product. Use 'data warehouse' for the general industry concept. | PostHogBase.ProductNames |
| 21:55 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 26:34 | warning | 'Trino's' is a possible misspelling. | PostHogBase.Spelling |
| 26:91 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
| 39:82 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'product analytics' for the general industry concept. | PostHogBase.ProductNames |
contents/docs/data-warehouse/warehouse/performance-tuning.mdx — 0 errors, 1 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 25:31 | warning | 'Trino' is a possible misspelling. | PostHogBase.Spelling |
contents/docs/data-warehouse/warehouse/setup.mdx — 0 errors, 3 warnings, 0 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 19:58 | warning | 'deprovision' is a possible misspelling. | PostHogBase.Spelling |
| 55:221 | warning | Capitalize 'Data Pipelines' for PostHog's product. Use 'Data pipelines' for the general industry concept. | PostHogBase.ProductNames |
| 63:12 | warning | 'deprovision' is a possible misspelling. | PostHogBase.Spelling |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ino engine Say in the hero and "What does it do?" that the Warehouse is a real database with its own hostname, credentials, and storage. Add a "BI & notebooks" slide to "How do I use it?". Replace the DuckDB and Postgres wire content on the query engine and storage slides with PostHog's fork of Trino. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This PR may affect SEO/AEO@natalia-amorim, please review the items below before this PR merges. If Natalia is out, ask Ian or Andy to review instead. 🔍 Worth a look (4)
This comment updates on each push. The check reads the diff only, so it can miss problems or flag safe changes. If this is a false alarm, reply here so the check can improve. |
| // The product lives at /warehouse, but its docs live at /docs/data-warehouse. | ||
| docsSlug: 'data-warehouse', | ||
| forumTag: 'data-warehouse', | ||
| teamSlug: 'warehouse', |
There was a problem hiding this comment.
P2 · Use the owning team's registered slug
On /warehouse, the “Who builds this?” section passes warehouse to SmallTeam, but the owning team's slug is managed-warehouse, as recorded in useFeatureOwnership and the product-team handbook. The lookup fails and renders plain “warehouse” text instead of the team name, crest, and link; set teamSlug to managed-warehouse.
…l time Add a "Events in near real time" row to the feature comparison. On US Cloud, new events land in the Warehouse within minutes of capture. EU Cloud does not stream events yet, so the PostHog cell says "US Cloud". Correct the Sources slide, which said that events update daily. Events arrive within minutes on US Cloud. Persons update daily. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… as unsupported - Remove the "Data management" and "Governance" sections - Show machine learning in the warehouse as not supported for PostHog Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…oduct-page # Conflicts: # src/pages/context-warehouse/warehouse.tsx
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
andyvan-ph
left a comment
There was a problem hiding this comment.
@Lizzieepton some more suggestions here. TL;DR: Since the product is called "Warehouse", we don't need to say "The Warehouse" we can just say "Warehouse".
Co-authored-by: Andy Vandervell <92976667+andyvan-ph@users.noreply.github.com>

Summary
This PR changes the Warehouse page from a custom page to the standard product page. It also:
/context-warehouse/warehouseto/warehouse, adds a redirect from the old URLPR tour
src/pages/warehouse.tsx(moved fromsrc/pages/context-warehouse/warehouse.tsx): the page is now one line that rendersProductReaderViewwith thedata_warehousehandle. The old custom page and its waitlist survey are removed.src/hooks/productData/data_warehouse.tsx: addsproductMenu, the overview copy, use cases, AI prompts, "Works with" cards, and the comparison rows. It also addsdocsSlug,forumTag, andteamSlug, because the product URL is not the same as the docs URL.src/hooks/productData/data_warehouse/slides.tsx(new): the "How do I use it?" tabs, the "Top features" tabs, and the page-specificGetAccesssection.src/components/CTAs/index.tsxandtemplates/Overview.tsx: add an optionalctaButtonsoverride. If a product does not set it, the buttons do not change.templates/CommunityQuestions.tsx: the "Check the docs" link usesdocsSlugwhen the product has one. Before this change, the link went to/docs/context-warehouse/warehouse, which does not exist.src/hooks/competitorData/{bigquery,snowflake,redshift}.tsxandProductComparisonTable: add three small competitor entries, so the table shows their names in the column headers. The row values are on the product data as custom rows.vercel.json: redirects/context-warehouse/warehouseto/warehouse. The two old redirects that went to/context-warehouse/warehousenow go to/warehouse, so there is no redirect chain.src/constants/productNavigation.ts: addsdata_warehouseaftertraces. Warehouse shows in the Products menu (under "More"), in the product-page switcher, and in the pricing calculator order.src/data/tools.ts(slug), the Context Warehouse sidebar and catalog,pairsWithin endpoints and group analytics, and links in blog posts, docs, and a customer story now use/warehouse.Reviewer's guide
CTAsandCommunityQuestionsfirst. These are the only changes that other product pages use. Both are optional and fall back to the current behavior.data_warehouse.tsx, and the sources are listed below. The table has no "Data management" or "Governance" sections. The Warehouse team confirmed the values, including ✗ for PostHog in "Machine learning in the warehouse".contents/docs/data-warehouse/warehousestill say "Join the waitlist" and link to this page. This PR does not change them.Checks
pnpm formaton the changed filestsc --noEmit: no new errors in the changed filesgatsby developstops insourceNodes./context-warehouse/warehouseand preview/warehouse. Both show the same error types (React Burger menu color fix #418/Small fixes for pricing and free trial pages #423 hydration, SVGwidth="auto"). No new error types./context-warehouse/warehouseredirect: not tested. The Cloudflare preview does not applyvercel.jsonredirects, so the old URL returns 404 there.pnpm test-redirects: the only suite it runs (scripts/seo-aeo-pr-check/check.test.js) fails on master too, because it importsnode:testunder Jest.Screenshots
Before is the live site (posthog.com). After is the deploy preview for 7069680. Narrow is 640px, wide is 1440px.
Warehouse page (before:
/context-warehouse/warehouse, after:/warehouse)Products menu (Warehouse is after Tracing)
Comparison sources
Generated by Claude Code
Update: Warehouse purpose and query engine (0c232b6)
This commit changes the product copy in
src/hooks/productData/data_warehouse.tsxandsrc/hooks/productData/data_warehouse/slides.tsx.Checks
prettierran on the two files.tsc --noEmitshows no errors in the two files.sourceNodesfailure. This commit has no screenshots. The "After" screenshots above do not show the new hero copy, the "What does it do?" copy, or the "BI & notebooks" slide.Open items
rootuser can write from an external client. docs(warehouse): reorient warehouse docs around Trino #21390 lists the same item.contents/docs/data-warehouse/surfaces/web-app.mdxsays that query repair in the SQL editor is the only place where PostHog AI touches the warehouse.Update: events in near real time (533a9ec)
EU Cloud does not stream events to the Warehouse yet, so the PostHog cell does not show a check mark. When EU Cloud streams events, change the cell to a check mark. Google's GA4 BigQuery Export docs say that streaming export makes data available within a few minutes.
Checks
prettierandeslintran on the two files.🤖 Generated with Claude Code