Use a supported_sources JSON column per tool, where each entry includes a connector slug, support status (GA, alpha, beta, deprecated), CDC mode, and incremental sync support. The connectors sheet drives per-connector pages that join every tool supporting the connector, with the tool's per-connector metadata exposed in the row.

A cdc_support column carries values like native_log_based, query_based, trigger_based, and limited, plus a cdc_sources JSON column with the subset of sources where CDC is available. The template renders a CDC badge and a CDC source chip grid, so readers see structured depth instead of marketing claims that flatten different CDC modes into a single yes.

Yes. The connectors sheet has its own ranking and verdict per connector. Per-tool pages handle solo views, and the connector ranking drives the ordered list on each /etl/{connector}/ page. Empty rankings can fall back to a templated rank derived from columns like CDC support and incremental sync.

Reverse ETL fits in a sibling page group with its own sheet, since the destination shape is different (Salesforce, HubSpot, Marketo instead of Snowflake or BigQuery). The two page groups can share a connectors sheet, with destination type filtering which group serves which connector page.

Add a hosting column with values like managed_cloud, oss_self_hosted, hybrid, and on_cloud. Render a /etl/open-source/ subset page filtered on oss_self_hosted, and let per-tool pages cover the long tail. The same row data drives both views, with the OSS page concentrating on teams that need to run the tool themselves.

Yes. A pricing_model enum supports values like mar_based, row_based, connector_based, capacity_based, and quote_only. The template renders the structured value as a badge and the pricing_note exposes the vendor's wording, so readers see honest framing rather than a forced dollar-per-row figure.

Yes. Map an image URL column to og:image via the meta type, so each per-tool page renders its own social card. For per-connector pages, the template can compose a connector badge OG. Pairing with SleekPixel lets the OG render on the fly from row data, overlaying tool name, connector count, and pricing model on a styled background.

Add a deprecated_sources JSON column per tool with source slugs and sunset dates. The template renders a small notice via selector mapping when the column is non-empty, so readers see current and deprecated coverage on the same page. The connector pages themselves can flag tools where the connector is on a sunset path.