docs: split feature engineering, move functions to Management

Feature engineering is now the overview plus one page per operation: add a
computed column, refresh a column, refresh a materialized view. Computed
columns covered declaring and filling on one page, which are separate decisions
with separate failure modes.

Functions move to Management, where the other catalog objects are, and absorb
the environment-mismatch guidance from the Enterprise page -- a symptom table
worth having beside the parameters that cause it.

The Enterprise feature-engineering page is merged into the overview. Two of its
claims were stale: create_materialized_view is implemented for db:// connections
in remote/db.py, so views are not local-only, and the tier is Enterprise rather
than 'Cloud and Enterprise'.

The REST reference leaves the sidebar. Mintlify only generates per-endpoint
pages from a navigation group -- hidden, dropdowns, global anchors and a
top-level openapi key were all tried -- so removing the group removes those
pages. The overview survives as an unlisted page, linked from SDKs & SQL, and
the spec still ships for anything that wants to read it directly.
This commit is contained in:
Jack Ye
2026-09-09 23:19:06 -07:00
parent c3f428acae
commit 8f37234a86
16 changed files with 372 additions and 199 deletions
@@ -19,4 +19,4 @@ The relevant section of the documentation are listed below.
|:--------|:------------|
| [Feature engineering](/feature-engineering) | The three ways to derive columns and tables. |
| [Materialized views](/feature-engineering/materialized-views) | Derive a table from a query and refresh it incrementally. |
| [Computed columns](/feature-engineering/computed-columns) | Declare a column from an expression and fill it. |
| [Computed columns](/feature-engineering/add-computed-column) | Declare a column from an expression and fill it. |