Atlas Content Modeler (ACM) was built by WP Engine for headless WordPress: a structured content modeler that registers each model as a custom post type and stores field values in standard wp_postmeta. Relationships live in a dedicated wp_acm_post_to_post table, and the modeler exposes the schema through both REST and WPGraphQL. The default admin lists rely on WordPress's standard columns, so the model definitions are rich but the post lists are still just title, author, and date.

SleekView reads ACM's registered models and gives each one its own table with the defined fields, taxonomies, and relationship slugs as proper columns. A "recipes" model can show difficulty, prep time, hero image, and related ingredients in one row. Sorting and filtering work correctly on number, date, and multiple-choice fields because SleekView reads the field type metadata from ACM's registry rather than treating every meta value as a string.

Inline edits to text, number, multiple-choice, and relationship fields go through ACM's own update functions, so any custom validation set on the field continues to apply, and any code subscribed to save_post or model-specific hooks fires as expected. Relationship updates write to wp_acm_post_to_post through ACM's API, which keeps the WPGraphQL and REST responses consistent without a separate sync job.

Atlas Content Modeler exists because the block editor is a great writing tool and a poor content modeler. It gives developers a UI for defining typed models, registers each one as a custom post type, and exposes the resulting schema through WPGraphQL and REST so a headless front end can consume it cleanly. The model definitions are rich and the API surface is genuinely good.

The admin is the part that has not caught up. The post lists for each model still show title, author, and date, while the typed fields that justify the model sit invisible in wp_postmeta. Editorial teams open posts one at a time to verify a difficulty rating or a prep time, and platform teams write throwaway scripts to audit field coverage during launches.

SleekView treats ACM models the way they were already structured: as rows and typed columns. Each model becomes a table, each field becomes a column, each relationship resolves inline. The schema does not move; the admin finally matches the model definition the rest of the stack already uses.