Skip to content
Dashboard Gallery
Get Support

Request a dashboard

When nothing in the gallery fits, you can describe what you need and the gallery will pass it on. This is the only thing on the site a visitor can write, and it needs no account.

There is no standing “Request a dashboard” button, and that is deliberate: the form appears at the moment you are already holding the thought.

  • Under a search answer. When the search tells you the nearest thing it has, the offer to request one is right there, and the form opens with your question already in it.
  • On an empty grid. When a filter combination returns nothing, the empty state offers it.
  • At #request on the gallery URL, which opens it with an empty field.

It opens in place, under the header — directly below the answer you are deciding against — rather than as a dialog over it. A dialog would hide the very answer you were reading.

FieldRequiredLimits
What do you want on it?Yes10 to 1,200 characters
EmailNoUp to 254 characters, and it must look like an address

The description is the whole of it. Naming the metric, the audience and the question the dashboard should answer is what makes a request buildable — the placeholder shows the shape:

Roaming failures by AP, so I can see which radios clients keep falling off.

The email address is optional and exists only so the request can be answered. A request with no address is a perfectly good request.

A duplicate check. Once you have typed enough, the gallery runs your half-written sentence through its own search and shows up to three dashboards that may already cover it. It is the same retrieval the search box uses, minus the model — so it costs nothing and takes no time worth noticing. If it fails for any reason it shows nothing at all: a duplicate check that could stop you asking for a dashboard would have inverted its own purpose.

When you reached the form from a search answer, the check does not re-run immediately — the answer above is the duplicate check for that sentence. It starts once you have changed enough of the draft for it to be your own question rather than the one you arrived with.

One clarifying question. Once the draft reaches about 40 characters, the gallery may ask a single question about it — the one thing that would most help whoever builds it. Answering appends your answer to the draft. It is entirely optional:

Or ignore this — the request sends either way.

If the day’s model allowance is spent, or anything else goes wrong, no question appears and the form is unaffected.

Submitting requires a Cloudflare Turnstile check, verified on the server against Cloudflare rather than taken from the page’s word for it. The widget loads only when the form is opened, so a visitor who never asks for a dashboard never fetches a bot-detection script.

It is the one third-party script on the public site, and it is loaded from Cloudflare rather than served from this origin — the script is the verification, so a local copy would mint tokens Cloudflare then rejects.

The rate limit in front of the form — 6 submissions per minute per address — is a smoother, not the check. Turnstile is the check.

You get a confirmation and nothing else:

That is in the queue to be built.

  • The request is never public. There is no endpoint that reads requests back — not even for the person who wrote it. Your words and your address are the only things in this gallery that were given rather than published, and the only route that can see them is behind the admin sign-in.
  • It arrives with the status new. Only the site owner can move it on, to planned, built or declined.
  • “N in the queue” beside the dashboard count is the number of requests at planned — reviewed and accepted for building. It is deliberately not the number submitted, because anyone can submit and nobody but the owner can promote. The segment is absent entirely when the number is zero, and it disappears while a filter is applied, since the queue does not respond to filters.

The gallery hides the form when the bot check is not configured, rather than showing a form that cannot succeed. The server refuses independently either way, so a form that appears is one that can work.