Toolset Blocks is the block-editor face of Toolset. Custom post types come from Types, custom fields are stored in wp_postmeta (with the wpcf- prefix for Types fields), and relationships live in the toolset_associations table together with toolset_relationships. The default Types admin uses the standard WordPress list screens with a few extra columns, which works fine for small models but becomes limiting once a site has dozens of fields per type and several relationships.

SleekView reads each Toolset post type directly and exposes every wpcf- meta field as a sortable, filterable column. The toolset_associations table resolves to inline parent and child cells, so a row from a Property type shows linked agents, photos, and amenities as proper columns. Repeating field groups expand into their own sub-view, and intermediate post types from many-to-many relationships are first-class sources in their own right.

Inline edits route through Toolset's Types API so the same hooks that fire on Forms submissions continue to apply, which keeps relationships consistent and any conditional logic registered in Types active. Saved views per role mean editors get the column set their workflow needs while developers get the full schema, and SleekView coexists with Toolset Views, Forms, and Access without overlap because it sits on top of the same Types data.

Toolset Blocks is excellent at modelling content and rendering it on the front end. Types defines the schema, Blocks renders it, and Views builds custom loops. The piece that's always been more work than it should be is the admin.

WordPress's default list screen is fine for editing one post at a time, but it doesn't show custom Types fields by default, and it has nothing to say about toolset_associations. Teams end up building Toolset Views just for the admin, which means designing templates and managing them on top of the actual content model. SleekView takes the admin off the Views path.

The same Types fields, the same relationship table, and the same hooks now power a sortable, filterable, inline-editable admin table without writing a template. Editors get a workable backend, developers stop building bespoke admin Views, and the Types schema stays the single source of truth.