Help us build Sleekplan.

We would like to collect NPS responses on the header of the default feedback widget instead of CSAT. Thus, an option to choose between CSAT and NPS would be nice.

Make it easy for me to access the main website from the admin portal, it took my colleagues and me ages to figure out where to find our main upvoting website from the admin portal!

I'd like to have the option to change the colors for the background and font for the single-post view and the start screen (header). I want a white background with black text for my single-post and a green background with white text for my header but I cannot do that right now.

When user is logged in, show its user avatar so that he can see at a glance that he is logged in

When clicking into the roadmap view on the widget, you can filter by category at the top. I'd like to be able to do the same thing with the changelog, including being able to set the default category.

Right now, the title appears to the right of the category chip. It would be easier to scan the list if it started on a new line like the mockup attached.

It would be great to make the widget of the Wordpress plugin multilingual. Or at least make all text-strings of the UI translatable in LocoTranslate. So we can keep the widget at the local Lock&Feal as of the website.

Description: Add a private flag to createcomment (and to updatecomment, so a comment can be flipped after the fact) that marks the comment as internal — visible to admins only, not to end users on the board. Today createcomment accepts only feedbackid, comment, parent and pinned.

Description: Add an optional author argument to createfeedback, accepting a userid or an email, so a post can be attributed to the end user it came from instead of to the authenticated MCP identity. Same reasoning applies to create_comment. Problem: Every post created through MCP

It would be useful if Access & Privacy settings could be configured independently for each section of a Sleekplan portal, rather than applying one privacy setting to the entire portal. Our use case We have different audiences and purposes for different parts of our portal. Fo