The format_support JSON column carries values like iceberg_read, iceberg_write, delta_read, delta_write, hudi_read, and hudi_write per platform. The template renders chips with tone classes derived from the suffix, so readers see read-only and read-write support as distinct states instead of a single yes or no field that hides the real story.

A catalog_support JSON column maps catalog slugs like unity, polaris, nessie, glue, and hms to read or write notes per platform. The template renders a catalog grid, and a /lakehouses/catalogs/ overview page can rank platforms by catalog coverage. Buyers see which catalogs work in both directions and which are read-only.

Yes. The formats sheet has its own ranking and verdict per format. Per-lakehouse pages handle solo views, and the format ranking drives the ordered list on each /lakehouses/{format}/ page. Empty rankings can fall back to a templated rank derived from columns like native_format and write support.

A query_engines JSON column carries engine slugs like spark, trino, dremio, presto, snowflake, and bigquery per platform. The template renders engine chips on per-lakehouse pages, and a /lakehouses/{engine}/ cut page ranks platforms by engine support. The same approach scales to new engines that gain Iceberg or Delta support.

Use acid_features as a JSON column with values like merge, delete, update, schema_evolution, and partition_evolution, plus a time_travel_days column. The template renders a feature grid and a time-travel stat, so readers compare structured semantics across platforms rather than editorial summaries.

Yes. A pricing_model enum supports values like dbu_per_hour, bundled_with_warehouse, credits, and quote_only. For platforms where the lakehouse is bundled with a warehouse, the page renders a clear bundled callout and the pricing_note exposes the actual unit and what it bundles with.

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

Add a vendor_extensions JSON column with extension slugs like uniform, deletion_vectors, liquid_clustering, and z_order. The template renders an extensions section per lakehouse, so readers see proprietary features in context without conflating them with format-standard capabilities.