Simplify content editing for a client
This workflow creates a smaller editing surface for a defined role while preserving the actions that person needs to create, review, and publish content.
Define the editor’s job
List the post types the editor uses, the required publishing actions, necessary taxonomies, custom fields, and whether the site uses the block editor or Classic Editor. Take screenshots of the current list and edit screens before hiding controls.
Configure content-list behavior
- Open Settings → POM Tweaks → Content → Editing.
- Enable Content duplicator and choose Allow duplication for these post types only where editors need duplication. Decide separately whether taxonomy terms and custom fields should be copied.
- Under Content → Lists, use Hide row actions to remove individual list-table links such as Quick Edit or Trash.
- Use Hide bulk actions only when every bulk operation for that post type should disappear.
- Under Content → Editing, enable Editorial notices, add a notice, and select Show this notice, its Post type, Title, and Message when the workflow needs permanent instructions.
- Open Settings → POM Tweaks → Content → Editing, enable Title length guidance, and configure Recommended maximum title length for the relevant Post types. This is advisory guidance in classic and block editors; it does not restrict imports or API requests.
Hidden row and bulk actions do not revoke their underlying capabilities. Treat them as interface simplification.
Reduce the edit screen
- Open Settings → POM Tweaks → White labelling → Metaboxes, enable the module, and click Discover panels for a representative item of the selected content type. Hide or remove only unnecessary panels, then click Save panel rules. These choices apply to all users on this site, including administrators.
- If the site uses Classic Editor, open Settings → POM Tweaks → Content → Classic editor and enable only the required buttons, palette, table, paste, class, or link controls.
- Do not use the TinyMCE components as a block-editor customization; they register classic-editor controls.
- Save a draft containing representative text, links, tables, media, taxonomy assignments, and custom fields.
Acceptance test
- Sign in as the client editor.
- Create, save, preview, publish, duplicate, and update one representative item.
- Confirm the duplicate contains or omits taxonomies and custom fields according to the selected options.
- Check the list screen for the intended row and bulk actions.
- Open a second post type that should remain unaffected.
- Repeat as an administrator to confirm that maintenance access remains available.
If the editor loses required data, restore the hidden panel or action first. Existing content is not deleted merely because its editor control is hidden.