Feature Requests

The Feature Requests page displays a public kanban-style roadmap where visitors can browse planned features, view details, and upvote the ones they care about most.

Overview

The Feature Requests page (/s) shows a horizontal kanban board with your product roadmap. Each column represents a stage in your development pipeline (e.g., Planned, In Progress, Completed), and visitors can browse tickets, read details, and vote to influence your priorities.

Kanban Board

A horizontal scrolling board with columns representing each stage of development.

Upvoting

Visitors can upvote features they want, helping you prioritize based on real demand.

Ticket Details

Click any ticket to see the full description, form fields, and screenshots in a slide-over panel.


Board Layout

The roadmap is displayed as a horizontal kanban board that fills the viewport. Each column shows:

  • Column name with a colored header line
  • Ticket count badge
  • Ticket cards sorted by upvote count (most popular first)

Only columns marked as public in your board settings are shown. Private columns remain hidden from visitors.


Ticket Cards

Each ticket card displays:

  • Upvote button with the current vote count (chevron-up icon)
  • Title β€” extracted from the first short text field in the ticket's form data
  • Description preview β€” extracted from the first long text field, limited to 2 lines

Tickets are sorted by their upvote count within each column, so the most requested features appear at the top.


Ticket Details

Clicking a ticket opens a slide-over panel with the full details:

  • Title and creation date
  • All form fields from the ticket submission, rendered by type:
    • Short text fields with labels
    • Long text fields with formatted content
    • Special "thank you" messages displayed as accent callouts
  • Screenshot if one was attached to the ticket

Upvoting

Visitors can upvote any feature request to show their interest. The upvote flow works as follows:

Click the upvote button

The visitor clicks the chevron-up button on any ticket card or in the detail panel.

Provide an email (first time only)

If the visitor hasn't voted before, a modal appears asking for their email address. This email is stored in a cookie for 7 days, so they won't be asked again on subsequent votes.

Vote is registered

The upvote count updates immediately. Clicking the button again removes the vote (toggle behavior).

Email collection serves two purposes: it prevents duplicate voting and allows you to notify voters when a feature ships.

Visibility Control

You control which columns appear on the public roadmap through your board settings in the dashboard. Mark columns as public to show them, or keep them private to hide work-in-progress stages from customers.

This lets you maintain an internal board with all stages while only exposing a curated view to the public.