Docs: Social Calendar Generation defaults and naming updates (408503)

[cursor]

Jira

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

Change classification

• UI / UX change
• Feature behavior change
• Configuration / system behavior

Summary of documentation updates

Updated existing documentation to reflect current Social Media Manager behavior and default Social Calendar Generation settings.

Files updated

• docusaurus/docs/ai/ai-workforce/index.mdx
  • Added Social Media Manager defaults section with current default model and schedule behavior.
• docusaurus/docs/fulfillment/task-manager/projects/create-and-manage-projects.mdx
  • Updated naming from old generation phrasing to Social Calendar Generation.
  • Added a defaults subsection for Social Calendar projects.
• docusaurus/docs/fulfillment/task-manager/projects/index.mdx
  • Updated Social Calendar project descriptions and FAQ wording to use Social Calendar Generation terminology.

Existing docs updated or new docs created

• Updated existing docs only
• No new docs created

Placement reasoning

• The behavior is specific to existing Social Calendar/Social Media Manager workflows.
• Best-fit locations are the existing AI Workforce overview and Task Manager project pages where users configure and understand these settings.
• A separate new page was not necessary and would fragment related guidance.

Acceptance criteria coverage

1. Rename feature from "Social Post Generation" to "Social Calendar Generation"
   • Covered by wording updates in Task Manager project docs and AI Workforce context.
2. Default AI model is "Gemini Flash Latest"
   • Explicitly documented in AI Workforce and project setup defaults sections.
3. Default trigger schedule values
   • Documented as:
     • Trigger type: On a Schedule
     • Frequency: Weekly
     • Day: Monday
     • Time: 9:00 AM
     • Timezone: from Business App/SMB timezone
     • Start date: current date
     • End date: no end date
4. Applicable to web and mobile
   • Explicitly documented.
5. Applicable to Social Media Manager
   • Explicitly documented.

Figma/images usage

• Jira screenshots were available as supporting context.
• No Figma links were present in the webhook payload.
• No new images were required for this update.

Skills used

• Repository skill reviewed: sprint-review
• Repository tools used for discovery and placement: rg, Glob, ReadFile

Validation

• npm run build (from docusaurus/) completed successfully.
• Existing repository-wide broken links/anchors were reported by the build and are unrelated to this change.
• npm run typecheck reports existing repo TypeScript issues unrelated to this documentation change.

Assumptions / limitations

• Jira metadata indicated a linked merged PR count, but no associated implementation PR with resolvable author details was discoverable via accessible GitHub searches by issue key (SM-3784), issue id (408503), or story title.
• To avoid incorrect/non-org tagging, no additional code-author mentions were added.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi