Cornerstone by Themeco stores its layout data inside the _cornerstone_data meta key on each page that uses it. The default Pages screen does not distinguish Cornerstone pages from any other page, which means an audit of Cornerstone-only content requires opening pages one at a time to check whether the front-end editor was used. SleekView reads the _cornerstone_data marker the same way Cornerstone itself does and shows only those pages, with template, author, last edited, and status as sortable columns.

The most expensive part of working with Cornerstone is opening the front-end editor, which boots a full visual editing environment for every page change. That is the right tool for layout work and the wrong one for renaming a page, fixing a slug, reparenting under a new section, or changing menu order, all of which are standard editorial work. SleekView edits the metadata around layouts inline, so a slug correction takes seconds instead of minutes of editor boot time. Layout edits still happen in Cornerstone, accessible directly from each row's launch action.

Site audits and editor handoffs are the typical workflows. The audit finds Cornerstone pages last edited over a year ago and surfaces them as candidates for refresh, archive, or unpublish. The handoff filters by author and status to give an incoming editor a clean list of the pages they need to take over without paging through ones owned by departed staff. Migration prep follows the same pattern: tag the Cornerstone pages, export, plan a rebuild on whatever target builder is next.

Cornerstone is a flexible front-end builder that does its job well, and the cost of that flexibility is editor weight. Booting the Cornerstone front-end editor for a single-character slug edit is operationally absurd, but it is what the default workflow requires because the Pages screen does not distinguish Cornerstone pages from any other content and quick edit hides the slug, parent, and template controls that editors actually need. The result is that small editorial work, the kind that should take a minute, ends up either deferred or done at full editor cost.

SleekView splits the work along the right axis: layout edits stay in Cornerstone where they belong, and metadata edits move to a tabular surface where they take seconds. The inventory part matters too. Sites running Cornerstone for any length of time accumulate pages from campaigns, redesigns, and one-off events that nobody cleaned up, and the default Pages screen makes that inventory invisible.

SleekView turns it into a query result. Cornerstone keeps doing what it does well; the surrounding editorial work moves off the heavy editor and onto a real list view.