Encyclopedia / Lexicon / Glossary (by twinpictures) keeps each entry as the encyclopedia custom post type with categories, tags, and a synonyms taxonomy linking related terms. The default admin list shows title, author, and date, useful for browsing but not for editorial work. Synonym coverage, related-term relationships, and entries with missing or short definitions all sit behind extra clicks.

SleekView reads the encyclopedia CPT and resolves its taxonomies into readable columns. Editors get a flat table where every term shows its category, synonym count, definition length, author, and last-update. Filters compose across those columns, so 'terms with zero synonyms and definitions shorter than 200 characters' becomes one saved view and one click. Stub entries, orphaned terms, and entries that need cross-referencing all surface together.

Inline edits cover status, category reassignment, and the synonyms taxonomy. Edits go through wp_update_post and wp_set_object_terms so any front-end glossary tooltip system, search index, or cache layer that hooks save_post refreshes as it would from the post-edit screen. CSV export of any saved view supports glossary audits and term migrations.

Glossaries grow by accretion and decay by neglect. Someone adds a term, fills in a paragraph, and moves on. Five years later the entry is still 38 characters long, has zero synonyms, and is buried in a category nobody curates.

The signal that this entry needs attention is sitting in the database the entire time, definition length, synonym count, last-update date, but the default admin shows none of it. Editorial leads have to open each term to know whether it needs work. That barrier kills audits.

A flat table with length, synonyms, category, and update-age as columns turns audit work from a chore into a sprint. Filter for stubs, fix them inline, move to the next category. Filter for orphans with zero synonyms, add cross-references in a single sitting.

The glossary becomes maintainable without anyone writing a custom report or running SQL against wp_posts and wp_term_relationships. SleekView delivers that without forking how the plugin stores its data.