The Wishlist is the public board for what the app should do next. Anyone can read it; with an account you can suggest a feature, vote for the ones you want, and now discuss any of them.This guide covers suggesting, the two budgets that keep the board honest, what the five statuses mean, and how discussion and moderation work.
Open Wishlist from the sidebar. Open items come first, ranked by votes; shipped and declined items follow, newest first. Each card carries its status, the vote count, and a link into its discussion with the number of comments.Two kinds of card live here. Roadmap items are written by the owner and are public from the start. Everything else is a user suggestion, which becomes public once it has been approved.
Suggesting something
Signed in, the top of the page has a title field and an optional details field. Say what you want to do, not how you think it should be built: "I want to read a story in German" is more useful than a spec.
A new suggestion is not public immediately. It waits for review, and while it waits only you can see it, marked Pending review. That keeps the board readable and spam-free.
This board is for features. For something broken, use report an issue instead - bugs get looked at on a different track.
Two budgets: five suggestions, five votes
You can have 5 open suggestions and 5 open votes at a time. Both counters are shown next to the compose box."Open" is the important word. A suggestion or a vote occupies a slot only while the item is still open, so shipping or declining an item frees the slot for everyone who backed it. Withdrawing a vote frees yours immediately.
The budgets are the point of the board. Five votes force a choice, which makes the ranking mean something: everything cannot be everyone's priority.
The five statuses
Under consideration - read, not yet decided. The default for a newly approved suggestion.
Planned - it is going to happen, no date attached.
In progress - being built now.
Shipped - done. Closed, and it frees every backer's vote slot.
Declined - not happening, usually with a public note explaining why. Also closed, and also frees the slots.
A declined item stays off the public board. The note is there so a decision is never a silent no.
Discussing an item
Every item has its own page, reached from Open discussion on its card. Anyone can read the thread; posting needs an account.Comments work exactly like story comments : one level of replies, a 15-minute window to edit what you wrote, and deleting leaves a placeholder so a conversation does not lose its shape. The comment count on the card matches what you see on the page, replies included.
A vote says "me too". A comment says why, which is far more useful when a feature could be built five different ways.
Moderation
Suggestions and comments both run through an automatic content check. Anything flagged is hidden pending review and stays visible only to whoever wrote it, with a note saying so. An admin then either restores it or leaves it hidden.Editing your own comment clears the previous verdict and re-runs the check, so a comment that was hidden over a single word can be fixed rather than lost.
Best practices
Vote before you write. If your idea is already on the board, a vote and a comment carry more weight than a duplicate entry.
Describe the outcome you want. The implementation is the part that changes once someone looks at it properly.
Spend your five votes on things you would actually use this month, and withdraw one when you change your mind.
Use the discussion to name your specific case. "I read with my kids and need shorter chapters" is the kind of detail that shapes a feature.
Under the hood
Both budgets are counted live from open items, never from a stored number, so shipping an item frees every backer's slot without a sweep.The vote count and the comment count are denormalised columns bumped inside the same transaction as the vote or comment, so the board is one bounded query rather than a count per row.An item is public only once it is approved AND has passed the content check. Setting any roadmap status on a pending item approves it, so a status can never leave an item invisible.Item pages are server-rendered for their metadata and reachable by link from the board. A pending, hidden or missing item answers 404 and its page is marked noindex.