Docs: update draft post-card scheduling in Manage Posts (387192)

[cursor]

JIRA

• https://vendasta.jira.com/browse/SM-3479

Change classification

• UI / UX change
• Feature behavior change

Summary of documentation updates

Updated existing Social Marketing documentation to reflect scheduling directly from draft post cards in Business App Social:

1. Updated existing page docusaurus/docs/social-marketing/posts/manage-posts-in-business-app-social.mdx

   • Added direct scheduling from Drafts post cards to feature highlights and included capabilities
   • Added a new procedural section: Step 4: Schedule a draft post
   • Documented visibility and validation behavior for the Schedule button
   • Documented confirmation message behavior after successful scheduling
   • Clarified limitations: content editing still requires Social Marketing, while scheduling from draft cards is supported
   • Added FAQ coverage for disabled Schedule button behavior

2. Updated existing index entry docusaurus/docs/social-marketing/posts/index.mdx

   • Refined the Manage Posts blurb so it matches current behavior (schedule draft posts + manage post states)

Existing docs updated vs. new docs created

• Existing docs updated: Yes
• New docs created: No

Placement reasoning

The behavior applies to the existing Manage Posts in Business App Social workflow, specifically the Drafts tab and draft post cards. Placing the update in that page keeps related actions together and avoids creating duplicate or fragmented scheduling guidance.

Acceptance criteria coverage

• Schedule button on draft post cards: Documented in Manage Posts steps and capabilities
• Supported for single-location and multi-location accounts: Documented
• Button visible only for draft-state posts: Documented
• Success confirmation after scheduling: Documented
• Date/time validation and disabled behavior for invalid schedule time: Documented
• Tooltip copy for invalid schedule time: Documented
• Tooltip copy for invalid schedule time + no valid social connection: Documented

Not documented (internal/implementation details not needed for end-user docs):

• Feature flag mechanics
• PostHog metrics instrumentation
• Backend API call topology

Figma / images usage

• JIRA screenshots and Figma links were provided in payload context.
• Direct authenticated access to attachments/Figma from this environment was not available.
• Documentation updates were grounded in explicit acceptance criteria and issue comments describing the final UI behavior and tooltip text.

Skills used

• .claude/skills/style-review/SKILL.md (including scan-style.sh)
• .claude/skills/pre-push-validation/SKILL.md (applied checklist for modified docs)

Assumptions / limitations

• No linked implementation PR with identifiable human code author was discoverable from accessible GitHub PR search for this issue key from this environment.
• Existing non-blocking style warnings related to legacy image naming/path patterns were left unchanged because they pre-existed and were outside this Jira scope.

Reviewers / tags

@ahnikakuse
@haleyserrano
@maryam6samadi