Documentation

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 dashboard prints, character for character
Addresses per key
10
a live site, a staging site, and room to spare

The guides

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

What every guide has to tell you

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.

Your own website

Take proposal requests where your customers already are

Your key and the addresses your form may appear on are on the plugin page in your dashboard. Paste two lines, and a board member reading your services page asks you for a proposal without leaving it.