Documentor uses a custom post type for documentation entries with parent/child relationships handled via WordPress's native post_parent column. Category and section data lives in standard term taxonomies. SleekView reads the CPT, joins the parent post, and pivots taxonomy assignments into named columns so editors see structure as data, not as a nested UI.

Yes. Parent assignment is editable in the row itself. SleekView writes back through the standard WordPress post API, so the frontend tree picks up the change automatically. Ordering writes to menu_order the same way drag-and-drop in the default editor would.

SleekView reads the CPT name dynamically — whichever slug your install uses. Older Documentor releases used different post-type slugs, and migrations from related forks can leave a non-standard name. The agent UI helps you point SleekView at the right one and discovers the meta keys automatically.

Yes. Any postmeta key on a doc entry can be surfaced as a column. Useful for tracking review status, last-verified dates, owner-team assignments, or any custom editorial flag your team uses. Pivot the relevant keys into named columns and they become sortable like any built-in field.

Yes. Ordering writes back to menu_order, which Documentor's frontend uses for sibling position inside a parent. Drag-and-drop ordering inside a parent works in the SleekView table the same way it does in the default editor's tree.

Yes. If your install registers multiple post types — say a separate "changelog" CPT alongside core docs — SleekView builds a tab per source on one page so editors stay on one screen instead of switching admin areas to triage each.

Yes. Any view exports to CSV with the visible columns, so a "docs needing review before launch" filter exports exactly the rows the editor sees. Useful for sharing with contractors or for handing a structured list to a project manager.

Yes. Entries whose post_parent points to a missing or trashed post show up with a flag column. That kind of orphan is invisible in a tree view because the entry never renders, but a flat table catches it immediately during cleanup passes.