Content types and collections

Your site has more than posts and pages. Workover reads the post types your site actually registers and lets you work with all of them.

Post types

When a project connects, Workover asks WordPress what post types exist — posts, pages, and whatever your theme or plugins add: products, case studies, docs, changelog entries.

Publishing a document, you choose which type it becomes. The choice is per document, so one project can hold blog posts and landing pages together.

Collections in the sidebar

The document list groups by post type, so you can look at just your posts, just your pages, or just one custom type.

Two things are worth knowing:

Drafts — documents not yet linked to any post — get their own group. That is where new writing lives before it has a home.
Internal post types are hidden. WordPress registers a lot you never want to see (navigation menus, reusable blocks, template parts, font families). Workover hides those by default rather than making you scroll past them.

Curating what you see

A site can register a dozen types and use three. Per project, hide the ones you do not work with — they are still there, still publishable, just not cluttering the list.

This is per project, because the answer differs per site.

Taxonomies

Each post type carries its own taxonomies. A post has categories and tags; a custom type may have its own. The WP panel offers the taxonomies that actually apply to the type you have chosen, rather than showing categories on something that has none.

If a term you need does not exist yet, Workover can create it on the site rather than sending you to wp-admin.

When a type is missing

If a post type does not appear, it is almost always because it is not exposed to the REST API — a custom type registered without show_in_rest is invisible to everything outside wp-admin, Workover included. That is a one-line change in the code that registers it.