@synap-core/workspace-templates 0.5.0 → 0.6.1

package/src/social.yaml

@@ -0,0 +1,246 @@
+# Social workspace template — distribution & publishing domain.
+# Plan, schedule, and publish across channels, then track how it performs: the
+# channels you own, the posts going out, the schedule that paces them, and the
+# engagement signals that come back. Consumes `content` + `marketing`,
+# provides `social`. Validated against types.ts at build time.
+
+meta:
+  slug: social
+  name: Social
+  description: "Plan, schedule, and publish across your channels — then track how each post performs. Channels, posts, schedules, and engagement signals, all connected."
+  icon: share-2
+  color: "#1D9BF0"
+  tags: [social, distribution, publishing, channels]
+  isPublic: true
+
+workspace:
+  name: Social
+  description: "The distribution layer — the channels you publish on, the posts and schedules that pace them, and the engagement signals that tell you what's working."
+  subtype: social
+  visibility: pod_visible
+  capabilities:
+    - social.channels
+    - social.publishing
+    - social.signals
+  sourceRoles:
+    content: consumer
+    marketing: consumer
+    social: provider
+
+profiles:
+  - slug: channel
+    displayName: Channel
+    icon: radio
+    color: "#1D9BF0"
+    description: "A social account you publish on — a platform, a handle, and its audience."
+    properties:
+      - slug: platform
+        label: Platform
+        valueType: string
+        inputType: select
+        enumValues: [x, linkedin, instagram, tiktok, youtube, facebook, threads, other]
+      - slug: handle
+        label: Handle
+        valueType: string
+        inputType: text
+      - slug: channel-url
+        label: URL
+        valueType: string
+        inputType: url
+      - slug: follower-count
+        label: Followers
+        valueType: number
+        inputType: number
+      - slug: channel-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [active, paused, archived]
+        constraints: { defaultValue: active }
+
+  - slug: social-post
+    displayName: Post
+    icon: send
+    color: "#0EA5E9"
+    description: "A single piece going out on a channel — its content, its schedule, and where it landed."
+    properties:
+      - slug: post-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [draft, scheduled, published, failed]
+        constraints: { defaultValue: draft }
+      - slug: post-channel
+        label: Channel
+        valueType: entity_id
+        targetProfileSlug: channel
+        inputType: entity_select
+      - slug: post-content
+        label: Content
+        valueType: string
+        inputType: textarea
+      - slug: scheduled-at
+        label: Scheduled For
+        valueType: date
+        inputType: date
+      - slug: published-at
+        label: Published At
+        valueType: date
+        inputType: date
+      - slug: post-url
+        label: Post URL
+        valueType: string
+        inputType: url
+      - slug: post-notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: post-schedule
+    displayName: Schedule
+    icon: calendar-clock
+    color: "#8B5CF6"
+    description: "A recurring cadence for a channel — the slot pattern that keeps posting consistent."
+    properties:
+      - slug: schedule-channel
+        label: Channel
+        valueType: entity_id
+        targetProfileSlug: channel
+        inputType: entity_select
+      - slug: cadence
+        label: Cadence
+        valueType: string
+        inputType: select
+        enumValues: [daily, weekly, biweekly, monthly, adhoc]
+      - slug: slot-time
+        label: Slot Time
+        valueType: string
+        inputType: text
+      - slug: schedule-notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: engagement-signal
+    displayName: Signal
+    icon: activity
+    color: "#10B981"
+    description: "A performance reading for a channel over a period — reach, impressions, and the reactions that came back."
+    properties:
+      - slug: signal-channel
+        label: Channel
+        valueType: entity_id
+        targetProfileSlug: channel
+        inputType: entity_select
+      - slug: reach
+        label: Reach
+        valueType: number
+        inputType: number
+      - slug: impressions
+        label: Impressions
+        valueType: number
+        inputType: number
+      - slug: likes
+        label: Likes
+        valueType: number
+        inputType: number
+      - slug: comments
+        label: Comments
+        valueType: number
+        inputType: number
+      - slug: shares
+        label: Shares
+        valueType: number
+        inputType: number
+      - slug: ctr
+        label: "CTR (%)"
+        valueType: number
+        inputType: number
+      - slug: signal-period
+        label: Period
+        valueType: string
+        inputType: text
+      - slug: captured-at
+        label: Captured At
+        valueType: date
+        inputType: date
+
+# CURATED views — the distribution motion, not one per profile
+views:
+  - name: Content Calendar
+    slug: content-calendar
+    type: kanban
+    scopeProfileSlug: social-post
+    groupBy: post-status
+    description: "Posts on a board by status — draft to published."
+  - name: Channels
+    slug: channels
+    type: table
+    scopeProfileSlug: channel
+    description: "The channels you publish on, with platform, handle, and audience."
+  - name: Signals
+    slug: signals
+    type: table
+    scopeProfileSlug: engagement-signal
+    description: "Engagement readings by channel and period."
+
+onboarding:
+  goal: >
+    Capture the real distribution motion — which channels you actually publish
+    on, what's scheduled to go out, and how it performs — so the workspace
+    mirrors how your audience gets reached, not a generic content plan.
+  framing: >
+    THE SOCIAL LEAD: Act as a sharp distribution lead. Anchor every post to a
+    real Content asset or a Marketing brief — social is the distribution arm, not
+    a separate content factory. Push for one channel done genuinely well over
+    spraying thin across five. Refuse "we post everywhere" — ask which channel
+    actually earns attention, and what the real cadence is.
+  collect:
+    - profileSlug: channel
+      what: The channels you actually publish on — one per real account, with its platform and handle.
+      cardinality: few
+      keyFields: [platform, handle]
+    - profileSlug: social-post
+      what: The posts in motion — drafts, scheduled, and recently published — each tied to its channel.
+      cardinality: several
+      keyFields: [post-status, post-channel]
+  openingQuestions:
+    - "Which channels are you actually active on right now, and which one earns the most attention?"
+    - "What's your posting cadence per channel — daily, weekly, ad-hoc?"
+    - "What's scheduled to go out next, and where does your content usually come from?"
+  doneWhen: at least one channel with a scheduled or published post.
+
+# App reference — no custom app for social
+app:
+  kind: stored
+  cellKey: entity-detail
+
+# Layout config for browser sidebar
+layout:
+  pinnedApps: [dashboard, data]
+  defaultView: Content Calendar
+  defaultApp: null
+  sidebarItems:
+    - kind: view
+      viewName: Content Calendar
+      label: Content Calendar
+      icon: calendar-clock
+    - kind: view
+      viewName: Channels
+      label: Channels
+      icon: radio
+    - kind: view
+      viewName: Signals
+      label: Signals
+      icon: activity
+
+# Bento dashboard
+bento:
+  viewName: Content Calendar
+  blocks:
+    - kind: view
+      viewName: Channels
+      pos: { x: 0, y: 0, w: 6, h: 5 }
+    - kind: view
+      viewName: Signals
+      pos: { x: 6, y: 0, w: 6, h: 5 }