Suggesting features
You sail with SailsSearch, so you know best what it is missing. Here is how to share ideas and help us decide what to build next.
Suggesting a feature
Look before you post
Someone may already have suggested your idea. If so, approve it and add your use case in the discussion — one well-supported request moves faster than several duplicates.
Describe the problem, not just the solution
Give your request a short, clear title. In the description, explain what you were trying to do, what got in the way and how the feature would help. Links to screenshots and examples are welcome.
Voting and discussion
Approve or decline
Every signed-in member has one vote per request. Approve the ideas you want, and decline the ones you think would make SailsSearch worse. Click your vote again to withdraw it, or switch it at any time.
Join the discussion
Comments and replies help us understand how a feature would really be used. Keep it friendly and on topic — the community code of conduct applies here too.
What happens next
Statuses
Every request starts as Open. When we start building it, it moves to In progress, and to Done once it has shipped. You can filter the list by status to see what is coming.
Moderation
Requests and comments appear immediately. Our team may hide spam, abusive content or anything else that breaks the code of conduct.
Formatting with Markdown
Requests and comments support Markdown. Type the syntax on the left to get the result on the right, and use the Preview tab to check your text before publishing.
**bold**
bold
_italic_
italic
~~strikethrough~~
strikethrough
`code`
code
[link](https://sailssearch.com)
- item - item
- item
- item
1. first 2. second
- first
- second
> quote
quote