User researchCAN I VIBECODE
Nolt?
BUILD FIRST
- One defined user and a repeatable end-to-end job
- A small, clear data model with sign-in only if it is genuinely needed
- Loading, empty, error, and success states that make the workflow feel complete
LEAVE FOR LATER
- Large integration marketplaces
- Multi-region scale and enterprise administration
- Every power-user setting from the established product
RESEARCH NOTES
What this tool actually does.
Nolt (nolt.io) is a hosted customer-feedback board and roadmap tool for collecting and tracking feature requests from idea to release. Users submit suggestions that others can upvote/downvote; boards support comments, attachments, following, and email updates. Admin capabilities: customizable statuses, custom fields, manual moderation, anonymous or identified voting, duplicate detection, and suggestion merging. Workflow: status tracking (planned, in progress, completed), automated status/comment emails to involved users, a board dashboard of engagement metrics, and change tracking on posts. Boards can be public or restricted by domain, password, or invite, with SSO. A public or internal roadmap reflects post status in real time; completed posts can auto-publish to a changelog. Requests can be segmented by custom attributes (plan, region, company size) to prioritize by customer impact, an
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a self-hosted web app inspired by Nolt's core feedback-board workflow: authenticated users submit feature suggestions; other users can upvote and comment; admins triage posts through a customizable status pipeline (e.g., New → Planned → In Progress → Shipped) and publish completed items to a separate changelog feed. Each post tracks its owner, vote count, comment thread, status history, and optional custom fields. Users can follow a post to receive notifications on status changes or new comments; admins can set board visibility (public, invite-only by email domain, or fully private), enable anonymous voting, open/close submissions, and manually approve posts before they appear. Include duplicate-detection heuristics (normalized title + description similarity) and a merge action that moves votes and comments from a duplicate into the canonical post. The roadmap view should show all accepted posts grouped by current status. Use a React (Vite) frontend with a Node.js/Express + SQLite backend, or Django + Postgres — choose one and justify it. Use JWT sessions, role-based access (visitor, member, admin), and a simple digest email worker (in-process queue) for notifications. Do not copy Nolt's brand name, logo, or visual design; build an original UI with accessible markup and a light/dark theme. Out of scope: SSO/SAML, SaaS billing, mobile native apps, real-time chat, Slack/GitHub integrations, and admin analytics beyond the basic board dashboard. For each core feature, include tests. Deliver a README covering setup, environment variables, seed data, and known limitations (e.g., duplicate detection is heuristic, emails only send in development mode unless an SMTP client is configured).