As a new user, I couldn't find a clear path to post in the Socra Community
Onboarded users face a 20 minute friction loop when attempting to contribute to the public community. While the platform's architecture correctly treats issues as the primary unit of work and the inbo
Hunter Johnson's day-zero journey identified a critical breakdown in the public community's posting flow. While the primary defect (silent failures on "Post" clicks) is resolved, several architectural and UI gaps remain under investigation.
!divider[Resolved]
The following "Post" button behaviors are fixed and verified for public routes:
* **Contextual Scoping:** Clicking "Post" from `/public/bugs` or `/public/general` now opens the composer scoped correctly to that space.
* **Root Defaults:** Clicking "Post" from the community root (`/public`) defaults to the General space.
* **Failure States:** Invalid submissions (e.g., empty titles) or network errors now trigger a toast notification with a "Retry" option instead of failing silently.
* **Filter Persistence:** The composer now respects the active space filter selected in the dropdown.
!divider[Open Defects]
The following issues from the original journey are tracked as separate tickets:
| Feature | Defect |
| :--- | :--- |
| **URL Routing** | `/community` returns a 400 error; intro text appears to be unedited model output. |
| **Navigation** | The globe icon in the sidebar lacks a hover tooltip and visible label. |
| **Cross-Context Posting** | Using "New Issue" from the Inbox or posting from within an existing thread scopes to the private workspace only; no "Publish to Community" toggle exists. |
| **AI Accuracy** | AI teammates incorrectly claim users cannot self-select into public spaces. |
!divider[Verification Needed]
@drhunter, please verify the fix in a clean state (sign out/in) across these scenarios:
* [ ] Post from `/public/general` lands in General.
* [ ] Post from `/public/bugs` lands in Bugs.
* [ ] Post from `/public` defaults to General.
* [ ] Space filter selection carries over to the composer.
* [ ] Error toasts appear on failed submissions.
> [!WARNING]
> The fix addresses silent failures, but "False Success" (Point 5 in the journey) remains. If a user clicks Post from inside a community thread and it opens a private workspace composer without warning, the user may inadvertently post sensitive data to the wrong destination.Hunter Johnson documents seven distinct UX failures encountered while attempting to file community bugs on his first day and files corresponding sub-defects. He identifies critical gaps in the onboarding flow, including broken UI elements and incorrect AI guidance regarding public space permissions.By Hunter Johnson