Space layout

[SimoneZaza]

Description

Our current Space layout is not effectively meeting the needs of our diverse user communities. Various issues have been identified:

• Knowledge Base: Some communities rely heavily on the knowledge base, while others rarely engage with it.
• Community Page: Despite the Community page being highly valued (as evidenced by its absence being greatly missed), user contributions remain low.
• Subspaces Page: The Subspaces page feels disjointed, positioned awkwardly between the Community and Knowledge Base sections, which are both integral to collaboration.

These observations highlight the need for a more cohesive and user-friendly layout that better supports our collaborative efforts.

Goal

For users to immediately understand what a Space is and how they can work with it

Hypothesis

What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit.

Must have scope

Define what is a must-have for launch and in-scope. Keep this section fluid and dynamic until you lock-in priority during planning.

Stakeholders

Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the Epic project.

Design

Figma file:
Comments are highly appreciated. When commenting in Figma, please also leave a note in the comments box below this issue to notify us