Yes, indirectly. Keep column_level_lineage, sql_lineage, and bi_lineage columns in the sheet, and let your editorial team update them as releases land. SleekRank reads whatever is in the source on the cache cycle, so the propagation is automatic once the row is updated. The detection itself is upstream of SleekRank, which handles the render layer, not the changelog monitoring layer.

Both page groups read from the same catalogs sheet. The capability group filters the rows at render time using the flag column matching the URL slug. A change to a catalog row updates every page that references the catalog, including per-tool, capability, and any category roll-ups, after the cache window expires.

Add columns for open_source flag, license, self_hostable flag, and a commercial_offering field where relevant. The per-tool page renders the open-source badge through tag mapping, and a dedicated /data-catalogs/open-source/ capability page lists every catalog with the flag set, sorted by GitHub stars or contributor count from a stats column.

Yes. Add a primary_warehouse column or a supported_warehouses array, and define a page group with the URL pattern /data-catalogs/{warehouse}/. The page filters the catalogs sheet by warehouse support and ranks by a warehouse_score column, producing pages tuned to readers looking for Snowflake or Databricks-first tooling.

Yes. The capabilities sheet has its own verdict column. The per-tool verdicts handle solo pages, and the capability verdict drives capability-specific recommendations. If a capability row's verdict is empty, the template can fall back to a templated summary built from the top three catalogs' verdicts.

Update the parent_company column or a discontinued flag plus a successor_slug column. Every page that references the catalog reflects the new owner after the cache window, and the discontinued banner renders via selector mapping. Add a 301 redirect to the successor page to preserve link equity for any backlinks the catalog earned.

Yes. Map an image URL column to og:image with the meta type, so each per-tool page renders its own social card. For capability pages, you can render an icon set or a count visualization. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying catalog name, lineage depth, and pricing model on a styled background.

Use a pricing_model column with values like sales_only, listed, or freemium, and a starting_price_disclosed flag. The per-tool page can render a sales-only badge through tag mapping where listed pricing does not exist, and category pages can filter to /data-catalogs/transparent-pricing/ subsets without rewriting the source data.