Duration

2 months (2023)

Tools

Figma (Design, Figjam), Github, Paper

The challenge

Dynamically segmenting content for different communities introduced significant technical complexity. Each community required nuanced control over what users could access, with its own lifecycle integrated into the broader StackUp experience. The scope and technical hurdles became difficult to justify within the project timeline.

Context

The multi-community publishing system was designed to control content visibility and manage distinct publishing lifecycles across different communities within StackUp.

The solution

After initial prototyping revealed the scale of complexity, we made the strategic decision to shelve the feature. This allowed the team to focus resources on core functionalities critical for launch, ensuring a robust foundation for the StackUp platform while keeping the door open for future iterations if demand warranted the investment.

In this case study

First cut

Second cut

Why we eventually (cut) it

First cut

Our initial attempt was scoped into the admin portal release. We explored a lightweight publishing interface allowing content to be visible across multiple communities — simple visibility toggles and status previews built into the admin flow.

Early prototype: publishing options built into the admin flow, with visibility toggles and status previews. View working proto here.