Update Manage Posts documentation for current workflows

[bkatusic]

Summary

• Align Manage Posts guidance with current filters, fields, status actions, and bulk actions.
• Update custom post type links to the local documentation route.
• Remove outdated screenshots and clarify publishing, viewing, trash, and deletion workflows.

Testing

• Not run (not requested)

Summary by CodeRabbit

• Documentation
  • Clarified how default WordPress posts and custom post types are managed.
  • Expanded search filter details, including statuses, keyword scope, date range behavior, and post limits.
  • Updated post creation and editing instructions, including required fields and the Publish action.
  • Clarified viewing, status changes, bulk actions, trash, and permanent deletion workflows.
  • Updated the Custom Post Types Extension resource link.

[coderabbitai]

Walkthrough

The Manage Posts guide now distinguishes standard posts from custom post types and clarifies search, creation, editing, viewing, status-change, trash, permanent-deletion, and related-resource instructions.

Changes

Manage Posts documentation

Layer / File(s)	Summary
Post scope, search, and creation sites/content/manage-posts.mdx	Clarifies supported post types, search filters and limits, and creation fields including slug and required/optional values.
Editing, viewing, and status changes sites/content/manage-posts.mdx	Updates editing and viewing steps, maps single-post status actions, and documents supported bulk status operations.
Deletion workflow and related resource sites/content/manage-posts.mdx	Clarifies trash and bulk permanent deletion, and changes the Custom Post Types Extension link to an internal route.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• mainwp/docs#81: Updates related Manage Posts and Custom Post Types documentation workflows.
• mainwp/docs#100: Makes similar Publish and trash/bulk-delete wording updates for Manage Pages.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the documentation-focused updates to Manage Posts workflows and current behavior.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs-review/manage-posts

---

_{Comment @coderabbitai help to get the list of available commands.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mainwp	🟢 Ready	View Preview	Jul 24, 2026, 1:51 PM

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@sites/content/manage-posts.mdx`:
- Around line 86-87: Update the “Title” and “Content” rows in the field
requirements table to mark both fields as required by changing their values from
“No” to “Yes,” while preserving the existing descriptions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 589d4edb-7919-42d5-afc6-4b928e5947fe

📥 Commits

Reviewing files that changed from the base of the PR and between 09f037c and 18d30d9.

📒 Files selected for processing (1)

• sites/content/manage-posts.mdx

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect the relevant document section and nearby context.
git ls-files sites/content/manage-posts.mdx
echo '---'
wc -l sites/content/manage-posts.mdx
echo '---'
sed -n '1,140p' sites/content/manage-posts.mdx

Repository: mainwp/docs

Length of output: 4285

---

🌐 Web query:

MainWP "manage posts" title content required docs.mainwp.com

💡 Result:

In the MainWP Dashboard, when creating a new post via the Manage Posts feature (found under Sites > Content Operations > Manage Posts), both the Title and the Content fields are required [1]. When using the Manage Posts interface: - Title: This is a required field used for the post title [1]. - Content: This is a required field used for the post body content [1]. These fields must be completed before you can proceed to select your child sites and publish the post [1]. Other fields, such as Excerpt, Custom Fields, Discussion Settings, Featured Image, Tags, and Categories, are optional [1]. If you are using the MainWP REST API to create posts, the post_title and post_content parameters are also essential components for the creation process [2]. Extensions like the Article Uploader also rely on these components, where, for example, the first line of an uploaded TXT file is treated as the title and the remaining text as the body [3].

Citations:

• 1: https://docs.mainwp.com/sites/content/manage-posts
• 2: https://docs.mainwp.com/api-reference/rest-api/posts
• 3: https://docs.mainwp.com/add-ons/posts-pages/article-uploader-extension

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

sed -n '70,95p' sites/content/manage-posts.mdx

Repository: mainwp/docs

Length of output: 935

---

Mark Title and Content as required. The MainWP form/docs treat both fields as required, so this table should show Yes for each.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@sites/content/manage-posts.mdx` around lines 86 - 87, Update the “Title” and
“Content” rows in the field requirements table to mark both fields as required
by changing their values from “No” to “Yes,” while preserving the existing
descriptions.