About this documentation

A note on how these docs are written, and how to flag anything that’s wrong.

This documentation is written with AI

I build SupaSidebar on my own. There’s no separate docs team, and not enough hours in the day to hand-write every page in a docs site this size. So these pages are drafted by AI alongside development, as features ship, and checked against the app’s source code as they’re written.

What that means for you

The docs stay close to the app, because they’re written from the same codebase the app is built from, often in the same sitting as the feature they describe. But mistakes can still slip through - a label that changed, a shortcut that moved to a different key, a step that no longer matches the current build.

Found something wrong?

Email admin@supasidebar.com - that’s the most direct way to reach me. Include:

• The page URL where you spotted the issue
• What the page says
• What you actually see in the app (a screenshot helps)

I reply within a couple of hours during waking hours, 12 hours at the latest, and fix the page as soon as I know about it.

You can also raise it in Discord  or open an issue on the docs GitHub repo .