Suggestions go through your account, separately from support requests. They are recorded, and an accepted one becomes a roadmap entry you can follow.
#What we promise, and what we do not
A submitted suggestion does not commit us to anything.
No approval, no date, and no promise that an accepted idea ships exactly as described. It is a suggestion rather than an order. We do read every one, and a real share of the theme's features grew out of them, so this is here to set expectations rather than to talk you out of writing.
#What this channel is for
Ideas that are useful to everyone using the theme.
A wish specific to one site is a different thing: that is custom work, with its own channel and its own terms.
#Two examples, side by side
A good request. "Add a Load More pagination mode to post listings, loading without a page reload." Any blog would use it, it works in every kind of listing, and it does not depend on a niche, a language or one particular site.
A weak request. "Add a field to the post card for my supplier's product code, shown under the title." One site in one niche needs it, and for everyone else it is an empty field cluttering the interface. Things like that are solved through filters and hooks, or through custom work.
#Check it yourself first
Who else would use this?
Can the existing settings already do it?
Is this actually a problem rather than a suggestion? Then it is a bug report.
That third question matters. A bug sent as a feature request waits in the wrong queue.
#What happens next
An accepted suggestion becomes a roadmap entry with a status you can follow. When it ships, it appears in the changelog, and the documentation section for it is updated.
That is the full cycle, and it is why a suggestion does not disappear into an inbox.
#Common questions
Can I see other people's suggestions?
Accepted ones appear on the public roadmap, where some entries carry votes you can add yours to.
How long until something is implemented?
A roadmap entry carries a rough period rather than a date, which is intent rather than a commitment.
My idea was declined. Can I ask why?
Yes, and the usual reason is scope, meaning it serves one site rather than the product, in which case there is often a way to achieve it with existing settings or a hook.
Can I pay to have my feature built?
That is custom work, which is a different conversation with different terms, and it is a legitimate route rather than a consolation prize.
I am unsure which channel to use
Something broken goes to support, something missing goes here, and something you need for one site goes to custom work, so when it is genuinely ambiguous send it to support and it will be routed for you.
#Still stuck
Open a support ticket if you are not sure whether your idea belongs here.
Last updated
