Skip to content

Docs: Social draft post-card scheduling behavior (387192)#420

Draft
cursor[bot] wants to merge 2 commits intomasterfrom
cursordocumentation-updates-automation-fbaa
Draft

Docs: Social draft post-card scheduling behavior (387192)#420
cursor[bot] wants to merge 2 commits intomasterfrom
cursordocumentation-updates-automation-fbaa

Conversation

@cursor
Copy link
Copy Markdown

@cursor cursor Bot commented Apr 1, 2026

JIRA

Change classification

  • UI / UX change
  • Feature behavior change

Summary of documentation updates

Updated existing documentation to reflect scheduling draft Social posts directly from post cards and the related validation/feedback behavior:

  1. Updated existing page: docusaurus/docs/multi-location-business-app/social/manage-posts-social-multi-location.mdx

    • Added a focused section for scheduling from draft post cards.
    • Documented visibility/state behavior (Drafts only, desktop + mobile toggle views).
    • Documented validation/error messaging:
      • Please select a future date and time to schedule this post
      • Please ensure the scheduled time is in the future and at least one social account is connected
    • Documented success snackbar feedback.
  2. Updated existing page: docusaurus/docs/business-app/demoing-business-app-to-clients.mdx

    • Extended the Social Marketing demo workflow to include scheduling directly from Posts > Drafts post cards.

Existing docs updated or new docs created

  • Existing docs updated only
  • No new pages created

Placement reasoning

  • This behavior belongs in existing Social posting workflows.
  • manage-posts-social-multi-location.mdx already covers Draft/Scheduled management actions and is the most direct place for post-card scheduling behavior.
  • demoing-business-app-to-clients.mdx already contains the end-user walkthrough for Social Marketing and is the correct place to keep demo instructions current.
  • Creating a new page would fragment closely related workflow guidance.

Acceptance criteria coverage

Mapped documentation updates to user-facing AC:

  • Schedule action available on draft post cards → documented in both updated pages.
  • Visible only for draft state → explicitly documented.
  • Supported in single-location and multi-location Business App Social contexts → represented via Business App demo workflow and Multi-location Manage Posts workflow.
  • Success snackbar after scheduling → documented.
  • Date/time validation for past values disabling scheduling → documented with exact user-facing message.
  • Combined invalid state message (past date/time + no valid social network connected) → documented with exact user-facing message.

Internal/non-doc AC items intentionally excluded from docs content:

  • Feature flag setup details
  • PostHog metrics implementation details
  • Backend API call sequencing details

Visual inputs used

  • JIRA screenshots and notes were used as supporting sources for UI state/message confirmation.
  • Figma/prototype links were referenced from the issue context; no additional assets were added to docs in this update.

Skills used

  • Read and followed repository skill:
    • /workspace/.cursor/skills/sprint-review/SKILL.md

Related PRs / contributors

Related PRs found for SM-3479:

No non-bot code contributor PRs linked to SM-3479 were discoverable from accessible GitHub search metadata.

Assumptions and limitations

  • Assumed this story is user-facing and already released (JIRA status Done, production verification comments in issue).
  • Relied on available JIRA text/comments/screenshots for behavior details where direct product UI access was not available.

Tags

@ahnikakuse
@haleyserrano
@maryam6samadi

Open in Web View Automation 

cursoragent and others added 2 commits April 1, 2026 11:25
Co-authored-by: Haley <haleyserrano@users.noreply.github.com>
Co-authored-by: Haley <haleyserrano@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant