The shared roadmap for Linked.Codes lives at /feedback. Anyone can read what's been suggested. Paying business accounts can post new ideas, report bugs, and vote on the queue.
Who can do what
Submit + vote — paid business accounts (lifetime or active hosting). Sub-users on your platform can read but can't post.
Manage — only the Linked.Codes team. We set the status (planned, in progress, shipped) and reply with admin notes when relevant.
Posting a good suggestion
A short, specific title beats a long vague one. The board sorts by votes — so a clear title is what gets you upvotes from people who feel the same pain.
- Title — one line. "Bulk-import links from CSV" is better than "Import feature".
- Type — pick Feature suggestion for ideas, Bug report for things that are broken.
- Details — what problem it solves. Skip the implementation guess; we'll figure that out.
You can edit your post by replying back through the link in your account, or post a new one.
Voting
Tap the upvote arrow on the left of any card. Tap again to remove your vote. Each post counts each user's vote once.
If your idea is already on the board, upvote it instead of creating a duplicate. We use vote counts to prioritise.
Statuses
The badge on each card tells you where it is.
- Open — under triage. Vote it up if it matters to you.
- Planned — committed to building. Usually within a few weeks.
- In progress — being worked on right now.
- Shipped — done. The release usually shows up in the changelog the same week.
- Declined — we're not going to build this. The admin note tells you why so you can find an alternative path.
Admin notes
When the team replies on a post, it shows up as a green callout under the body. We use it to ask clarifying questions, share progress, or explain a decline.
Why public
Two reasons. First, the queue itself is useful — even before you sign up, you can see whether something you care about is on the way. Second, public votes mean we build things people actually use, not what we think they'd use.