codanomiq · Documentation and support

Written down, and answered.

Thirty-seven guides inside the admin, searchable in full text, from a first afternoon to the developer reference. And a support desk on the same screen, which tells you what it promises before you write to it.

Ask us anything
Help & supportSearchTickets
Guides37
Visible to this reader25
SearchFull text, gated
Open tickets2
Help & supportDemo data
37 guides · Full-text search · Help that opens the right heading · Tickets in the admin · On every install

What is there

In the admin as · Help & support
01

From the first afternoon

Getting started, the questions people actually ask first, and a guide for every tool — pages, canvas, assets, listings, events, menus, the shop, the hotel, hiring, the mailer.

02

Down to the developer reference

Architecture, the plugin contract, every app’s endpoints, the token grammar, templates as data, agent access. The same documents we build from.

03

Searchable in full text

Type a phrase, get the paragraph. Results name the guide and the heading and land you on it, with the words you searched for marked.

04

Help where the question is

The ? beside a field opens the exact heading that explains it — and brings you back to where you were, rather than dumping you at an index.

05

Three kinds of ticket

Something is broken, a suggestion, or I need help. Raised from the admin, tracked at an address you can return to.

In the admin as · Support
06

Answers come back to you

A reply or a status change arrives in your notifications, so the conversation is where the work is rather than in an inbox.

The tool itself

Click any screen for a larger view

A demonstration installation, with invented data.

01

You are only shown the parts that are yours

The manual is filtered by the same permissions as the product. A person whose group has no Shop sees no shop guide; the developer reference needs developer access; a tool you have not bought is not described to you.

The part worth saying out loud is that the search is filtered too, against the source rather than the rendered page. Gating only what is displayed leaves a search box that will happily quote you two paragraphs of a document you are not allowed to open — which is not a documentation feature, it is a disclosure.

02

Each kind of ticket says what it promises, before you write it

  • Something is broken. You get automated updates as it is looked at and fixed. Nobody replies in words — the status changing is the reply.
  • A suggestion. You get an acknowledgement and nothing more. Every one is read; we do not answer them individually.
  • I need help. A person reads it and replies.

Those sentences are on the form, above the box, not in the small print afterwards. A form that takes a suggestion and then never replies has not failed — it has misled, and somebody is left waiting for an answer that was never coming.

03

It is part of the product, not a website somewhere else

The guides live inside the admin, so they are the guides for the version you are running rather than for whatever is current on a marketing site. They are updated in the same change as the feature they describe — that is a rule we hold ourselves to, not an aspiration.

And there is no separate support portal to be given an account on, no second password, and no forgetting which address to write to. It is a screen in the thing you were already using.

Nobody reads the manual.

Which is why it is searchable, why the help icon goes to the paragraph rather than the index, and why the support desk is on the same screen. The measure of documentation is not how much of it there is. Get in touch →

Back to the platform →