As a user,
I want the start experience to present clear and separate flows for finding people, discovering communities, and creating my own community,
so that I can easily understand what actions are available without feeling overwhelmed or confused.
Acceptance Criteria
The application start view is redesigned into a simplified dashboard experience
The start view no longer contains large combined lists of servers and users
The start view contains clear primary action sections/cards for:
Find People (Purple)
Find Communities (Blue)
Create Community (Green)
Each primary action navigates to its own dedicated page/view:
/people
/communities
/create-community
Sidebar navigation is simplified and does not contain redundant “Home” functionality
The dashboard/start view acts as the primary landing experience
Start View Behavior
The start view displays:
Search input
Quick actions
Suggested or recent content
Onboarding-friendly empty states
Search functionality supports:
People
Communities
Invites
Search results are grouped into categorized sections
Dedicated Find People Page
The Find People page contains:
Search users
Suggested users
Mutual/community-based discovery
“People You Might Know” is initially empty for new users
Empty state behavior for new users:
Friendly onboarding message is displayed
Guidance explains that users will appear after joining or browsing communities
Example empty state messaging:
“Join communities to discover people with shared interests”
Suggested users begin populating only after:
User joins communities
User browses communities
Shared memberships or interactions exist
User discovery is based on:
Shared community membership
Recently interacted communities
Existing social graph data
Dedicated Find Communities Page
The Find Communities page contains:
Community search
Featured communities
Trending/recommended communities
Recently active communities
“Recently Active Communities” is hidden or replaced with onboarding content for new users with no browsing history
Empty state behavior for new users:
Display featured/trending communities instead
Explain how activity and recommendations will appear over time
Example onboarding message:
“Explore communities to personalize your recommendations”
Dedicated Create Community Page
The Create Community page contains:
Create from scratch option
Community templates/categories
Simple onboarding flow
Advanced configuration options are hidden initially
Community creation flow prioritizes simplicity for non-technical users
Technical terminology is minimized where possible
UX / UI Requirements
Navigation hierarchy is simplified to reduce cognitive load
Duplicate navigation paths are removed
Dashboard focuses on tasks rather than administration
Cards/buttons use descriptive labels and supporting text
Interface prioritizes progressive disclosure:
Advanced settings are hidden until needed
Empty states are visually polished and informative
UI remains consistent with existing dark theme and Tailwind styling
Layout supports desktop-first experience while remaining responsive
Definition of Done
Start/dashboard view is redesigned and implemented
Dedicated pages for:
Find People
Find Communities
Create Community
are fully functional
Redundant navigation items are removed
Empty states for new users are implemented
User recommendations populate dynamically after community interaction
Community recommendations work with and without user history
Search supports people, communities, and invites
UX is validated for non-technical users
Layout and components are implemented consistently using Tailwind CSS
Functionality is tested for both new and returning users
> As a user,
> I want the start experience to present clear and separate flows for finding people, discovering communities, and creating my own community,
> so that I can easily understand what actions are available without feeling overwhelmed or confused.
---
### Acceptance Criteria
* The application start view is redesigned into a simplified dashboard experience
* The start view no longer contains large combined lists of servers and users
* The start view contains clear primary action sections/cards for:
* Find People (Purple)
* Find Communities (Blue)
* Create Community (Green)
* Each primary action navigates to its own dedicated page/view:
* `/people`
* `/communities`
* `/create-community`
* Sidebar navigation is simplified and does not contain redundant “Home” functionality
* The dashboard/start view acts as the primary landing experience
---
### Start View Behavior
* The start view displays:
* Search input
* Quick actions
* Suggested or recent content
* Onboarding-friendly empty states
* Search functionality supports:
* People
* Communities
* Invites
* Search results are grouped into categorized sections
---
### Dedicated Find People Page
* The Find People page contains:
* Search users
* Suggested users
* Mutual/community-based discovery
* “People You Might Know” is initially empty for new users
* Empty state behavior for new users:
* Friendly onboarding message is displayed
* Guidance explains that users will appear after joining or browsing communities
* Example empty state messaging:
* “Join communities to discover people with shared interests”
* Suggested users begin populating only after:
* User joins communities
* User browses communities
* Shared memberships or interactions exist
* User discovery is based on:
* Shared community membership
* Recently interacted communities
* Existing social graph data
---
### Dedicated Find Communities Page
* The Find Communities page contains:
* Community search
* Featured communities
* Trending/recommended communities
* Recently active communities
* “Recently Active Communities” is hidden or replaced with onboarding content for new users with no browsing history
* Empty state behavior for new users:
* Display featured/trending communities instead
* Explain how activity and recommendations will appear over time
* Example onboarding message:
* “Explore communities to personalize your recommendations”
---
### Dedicated Create Community Page
* The Create Community page contains:
* Create from scratch option
* Community templates/categories
* Simple onboarding flow
* Advanced configuration options are hidden initially
* Community creation flow prioritizes simplicity for non-technical users
* Technical terminology is minimized where possible
---
### UX / UI Requirements
* Navigation hierarchy is simplified to reduce cognitive load
* Duplicate navigation paths are removed
* Dashboard focuses on tasks rather than administration
* Cards/buttons use descriptive labels and supporting text
* Interface prioritizes progressive disclosure:
* Advanced settings are hidden until needed
* Empty states are visually polished and informative
* UI remains consistent with existing dark theme and Tailwind styling
* Layout supports desktop-first experience while remaining responsive
---
### Definition of Done
* Start/dashboard view is redesigned and implemented
* Dedicated pages for:
* Find People
* Find Communities
* Create Community
are fully functional
* Redundant navigation items are removed
* Empty states for new users are implemented
* User recommendations populate dynamically after community interaction
* Community recommendations work with and without user history
* Search supports people, communities, and invites
* UX is validated for non-technical users
* Layout and components are implemented consistently using Tailwind CSS
* Functionality is tested for both new and returning users
myxelium
added this to the Zoracord 1:1 project 2026-05-25 19:33:04 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Acceptance Criteria
The application start view is redesigned into a simplified dashboard experience
The start view no longer contains large combined lists of servers and users
The start view contains clear primary action sections/cards for:
Each primary action navigates to its own dedicated page/view:
/people/communities/create-communitySidebar navigation is simplified and does not contain redundant “Home” functionality
The dashboard/start view acts as the primary landing experience
Start View Behavior
The start view displays:
Search functionality supports:
Search results are grouped into categorized sections
Dedicated Find People Page
The Find People page contains:
“People You Might Know” is initially empty for new users
Empty state behavior for new users:
Example empty state messaging:
Suggested users begin populating only after:
User discovery is based on:
Dedicated Find Communities Page
The Find Communities page contains:
“Recently Active Communities” is hidden or replaced with onboarding content for new users with no browsing history
Empty state behavior for new users:
Example onboarding message:
Dedicated Create Community Page
The Create Community page contains:
Advanced configuration options are hidden initially
Community creation flow prioritizes simplicity for non-technical users
Technical terminology is minimized where possible
UX / UI Requirements
Navigation hierarchy is simplified to reduce cognitive load
Duplicate navigation paths are removed
Dashboard focuses on tasks rather than administration
Cards/buttons use descriptive labels and supporting text
Interface prioritizes progressive disclosure:
Empty states are visually polished and informative
UI remains consistent with existing dark theme and Tailwind styling
Layout supports desktop-first experience while remaining responsive
Definition of Done
Start/dashboard view is redesigned and implemented
Dedicated pages for:
are fully functional
Redundant navigation items are removed
Empty states for new users are implemented
User recommendations populate dynamically after community interaction
Community recommendations work with and without user history
Search supports people, communities, and invites
UX is validated for non-technical users
Layout and components are implemented consistently using Tailwind CSS
Functionality is tested for both new and returning users