Studio Features for Phase 2: Communication & Sharing
Studio Features for Phase 2: Communication & Sharing
Highlighted communication & collaboration touchpoints across the Studio surface
Framing
For this post, I am outlining a list of features within the Studio area that directly align with our current Phase 2: Communication and Sharing. Studio unifies authoring and collaboration into one continuous surface rather than treating them as separate categories connected by cross-links.
Refer to Feature Areas, Functions & Relationships-> for more info about the Studio Feature Area.
Each interaction point is tagged Necessary or Wishlist.
And this classification is open for feedback and change
Chapter 1: Post-Level Communication
Communication and collaboration modeled loosely on Google Docs’ comment architecture — discourse anchored directly to content and attached to the post itself.
1. Comment section attached to every post
Category: Asynchronous CommunicationStatus: NECESSARYA baseline social layer attached to every published post. Without it, a post is a solo artifact with no attached discourse — breaking the premise that making and sharing are one act.
2. Inline highlight-to-comment (text or image)
Category: Asynchronous Communication × Visual/Page EditorStatus: NECESSARYUsers can highlight a span of text or an image region on a post and attach a comment directly to that spot. This is the direct multiplayer expression of the editing act itself — comments attach to the specific thing being made, not just to the post as a whole.
3. Bidirectional link between inline comments and comment section
Category: Asynchronous CommunicationStatus: NECESSARYInline comments surface in the comment section, and clicking a comment there jumps to and highlights the connected spot on the post. Functions as connective tissue between Features 1 and 2 rather than a standalone feature.
Note: Without this link, Features 1 and 2 read as two disconnected systems rather than one coherent comment architecture.
4. Tag people on post creation → notification
Category: Asynchronous Communication
Status: NECESSARYWhen creating a post, the author can tag people who need to see it, triggering a notification to them.
Note: Necessary on usability grounds rather than the parallel-features principle — people can’t participate in something they don’t know exists.
5. Live cursor indicators on active page
Category: Presence & AwarenessStatus: WISHLISTShows a live cursor indicator for other users actively viewing or editing the same page/post in real time.
Note: Structurally aligned with the parallel-features principle, but reclassified as Wishlist on MVP-timing grounds — a real-time position-broadcast feature carries meaningfully higher engineering cost than the async features above.
Chapter 2: Cohort Communication & Notification
Communication and awareness at the cohort level— group-wide broadcast, shared discussion, presence, synchronous coordination, and unread-state signaling.
1. Announcement board for team-wide updates
Category: Asynchronous CommunicationStatus: NECESSARYA one-to-many broadcast channel for cohort-wide updates, distinct from peer discussion.
Note: Without this, important updates get buried in threaded discussion or scattered across individual posts.
2. Threaded cohort-wide discussion (splittable by topic)
Category: Asynchronous CommunicationStatus: NECESSARYA shared discussion space for the cohort, able to be split into separate threads per topic.
Note: The cohort-level equivalent of the post-level comment section — without it, a cohort has no home for coordination that isn’t tied to a specific piece of content.
3. Status markers for who is online
Category: Presence & AwarenessStatus: NECESSARYLightweight online/offline indicators for cohort members.
Note: A much lower engineering lift than live cursors, and foundational to making a cohort feel like a populated space rather than a static list of names.
4. Video calling
Category: Synchronous CommunicationStatus: WISHLISTLive video calling among cohort members.
Note: Highest-cost feature in this chapter (real-time AV infrastructure, likely third-party integration). Structurally a strong multiplayer expression of cohort collaboration, but separated as an MVP-timing call — cohorts can coordinate synchronously via external tools without breaking the core Studio experience in an early version.
5. Unread visual marker on post previews in cohort feed
Category: Presence & Awareness × Asynchronous CommunicationStatus: NECESSARYA visual marker on post previews in the cohort feed indicating posts the user has not yet opened.
Note: Without this, users can’t distinguish new from already-seen content, undermining the cohort feed as a communication surface rather than just a content list.
6. Short status updates on cohort profile (“what I’m working on”)
Category: Presence & AwarenessStatus: WISHLISTUsers can add short, self-authored status updates to their profile within the cohort so others are aware of what they’re currently working on.
Note: A soft-social/context feature rather than a structural requirement of the parallel-features principle — useful for cohort cohesion, but the cohort functions without it. This feature is based on the original OSS platform, where users could drop in a very brief bio or status sentence to their accounts on a cohort page.
Chapter 3: Personal Activity & Notification Center
The aggregation point that pulls activity from all communication streams a user belongs to — post-level, cohort-level, and direct — into a single personal surface.
1. Direct messaging to other users
Category: Synchronous / Asynchronous CommunicationStatus: NECESSARYOne-to-one direct messaging between users, independent of any specific post or cohort.
Note: The first purely personal (non-cohort, non-post) communication channel in the paper — without it, all communication is tied to a piece of content or a group, with no space for direct peer contact.
2. Notification center: mentions and comment replies
Category: Asynchronous Communication Status: NECESSARYPulls in notifications when a user is mentioned or when someone replies to their comment, across posts.
Note: Direct aggregation of the comment architecture built in Chapter 1 — without this landing point, mentions and replies have no personal surface to resolve to.
3. Cohort announcements surfaced in personal center
Category: Asynchronous CommunicationStatus: NECESSARYAnnouncements posted to a cohort's announcement board (Chapter 2, Feature 1) also appear in the user's personal center.
Note: Ensures cohort-wide broadcasts reach members without requiring them to actively check each cohort's board.
4. Post activity & versioning/remix digest
Category: Asynchronous Communication × VersioningStatus: WISHLISTAggregates activity on posts a user authored — new comments, likes, and remix/version activity where another user has built on or branched from their work.
Note: The natural personal-facing counterpart to the Chapter 1 comment section, and the first place Versioning — one of the five nested feature areas — gets a communication/notification expression in this paper. Without it, authors have no way to know their post is generating discourse or being built upon unless they manually revisit it.
5. Tagged-post notifications land in personal center
Category: Asynchronous Communication Status: NECESSARYNotifications triggered by being tagged on post creation (Chapter 1, Feature 4) surface here.
Note: Chapter 1 built the trigger; this is where it has to land for the loop to close.
6. Unread / all-caught-up state for the activity center
Category: Presence & Awareness Status: WISHLISTDistinguishes new activity from already-reviewed activity across the aggregated feed.
Note: Same logic as the Chapter 2 unread marker on the cohort feed, applied here to the personal aggregation surface.
7. Filtering/grouping by source (cohort, post, person)
Category: Asynchronous Communication Status: WISHLISTLets users filter or group the activity feed by which cohort, post, or person the activity came from.
Note: Useful once activity volume grows, but the center functions without it early on — a refinement rather than a structural gap.
Comments