Use
Run the samples
Clone the library, open a dummy board, and keep prepare → start → read → stop. That is already participation.
Field guide
Community
This site is static. There is no live forum or comment database. Community here means a shared way of working: read the maps, reuse the session lifecycle, and leave a trail others can follow.
Where to go
Docs
Learn the session
Boards, install, data format, and samples. Start here before you invent a new call order.
Open docs →Reference
Look up a signature
Modules, arguments, and return shapes. The same four session calls in every language binding.
Open reference →Journal
Read a field note
Short essays on presets, markers, and release habits. No login. No thread.
Open blog →About Us
Meet the workshop
People, license, and platforms. The public face of Ability is this site, not a member list.
Open About Us →House rules
-
01
Search first
Docs, then Reference, then the journal. Repeat the four session calls if you write to someone.
-
02
Show a log
Device id, preset, and the block shape you got. A paste beats a screenshot of code.
-
03
Stay kind
Correct the map, not the person. No vendor fights. See About Us for people and license.
How to take part
Write
Keep a note
If a preset map surprised you, write it down like the journal does. Static pages beat a disappearing chat.
Reach
Send a letter
For a broken read or a missing board, use Ask Help. There is no inbox behind this page and no live counter.
Ask Help →Questions we already answered
Where do I post a question?
You do not post it here. This page does not store threads. Use Ask Help for contact, or read Docs and Reference first.
Is there a chat or member list?
No. Ability’s public face is this static site. No accounts, no comments, no database. The “room” is the shared API and the notes in the journal.
How do I report a bug?
Include device id, preset, language binding, and the four session calls. Send that through Ask Help so it arrives as mail, not as a row in a table we do not run.
Can I contribute a page?
Yes, as a file. Follow the Docs/Reference heading pattern, keep Ability copy (not another library’s), and send it the same way you would a bug note.