HOAcrew

Docs

Putting HOAcrew on your own website

These are the technical guides. They are written for whoever looks after your site, whether that is you on a Saturday morning or an agency on a retainer, and every step names the actual screen and the actual button.

Platform guides
7
one page each, no scrolling past somebody else’s
Reference guides
2
the security model, and the blank-form fix
What you paste
Two lines of HTML
the same string your console prints, character for character
Addresses per key
10
a live site, a staging site, and room to spare

The guides

One guide ships today, and it is the whole of it — the overview, a page per platform, the options, the events it fires, and the security model.

Proposal request plugin

Two lines of HTML that put a proposal request form on your own website. A board member reading your services page asks you for a proposal without leaving it, and the request arrives in your console addressed to your company alone.

Included with HOAcrew+ · about ten minutes

Read the guide

Straight to your platform

The install steps are one page per platform rather than one long page with 7 headings, so nobody scrolls past WordPress to reach Squarespace. Each of these opens on the three steps for that builder, and names the menu item you are looking for.

Reference

Two pages that belong to every platform at once rather than to any one of them.

The security model

What the key can and cannot do, what is stored, and where the edges are. The page to forward to whoever asks.

The form is not showing up

The one failure with no error message, its usual cause, and the two-minute fix.

What every guide has to tell you

The snippet is Two lines and one of them is a <script> tag, which means it is somebody else’s code running on your website. Every guide here therefore carries a plain-English section on what that code can reach, what it records, and where the edges of that are.

Anything that runs on somebody else’s website says what it does.

If a page here ever leaves that section out, it is a defect in the page, not an omission you are meant to read past. The security model is its own guide.