Almost everything here is a guide, an SOP, or a hub.
Guide
What a reader follows
A step-by-step document — numbered steps, screenshots, the tools each step needs. A guide belongs to your account, not to any one hub, and the same guide can appear in as many hubs as you like. There is still one of it to edit.
SOP
What a process is
A procedure for the person running the work, not only the person doing it. An SOP embeds the guides it depends on, so change a guide and every SOP that embeds it stays current.
Hub
Where an audience reads
A help center of its own — its own address, logo, accent color, and wording. Publish one under your own name, or one per client under theirs, and it holds exactly what you published to it.
Docs is the word for all of it together: every guide and SOP in your account. When a hub publishes, it publishes docs.
The screenshot files itself into the step.
Writing documentation is hard, and the slow part is not the typing — it is the screenshot: taking it, finding it, cropping it, and dropping it in the right place, every time the screen changes.
Capture from the browser
The Docssier extension takes the shot from the page you are on and files it into the step you are writing. It does not stop at your Downloads folder.
Nothing secret is written down
Typing is recorded as a step, and a password, card number, email, or phone value is never written into a guide — only the name of the field it went into.
Mark it up, then publish
Blur, zoom, and pointers live in the step editor, and a draft is visible to nobody until you publish it. Install it from the Chrome Web Store — Chrome and Chromium browsers.
A help center, not a share link.
A hub is a real website at its own address, not a link that expires the moment someone forwards it, and it reads as though it belongs to whoever opens it.
An address each, under any brand
Publish one hub under your own name, or one per client under theirs. The type and layout stay Docssier's, so it reads as calm whatever color is picked.
One library behind them all
The same guide can sit in many hubs at once, current in all of them, because publishing places a guide rather than copying it. Correct it once, and every hub holding it is correct.
Docssier, twice and quietly
On a client's hub, Docssier appears only as two lines — Published with Docssier in the footer, Powered by Docssier in the chat. Everything else on the page is theirs.
Three ways to read the same guide
A published guide can be read as a scrolling Article, as Slides one step at a time, or as a Movie that advances through the steps on its own. The reader picks; you publish once.
When reading leaves a question, the chat answers it.
Doc AI answers from that hub's published docs and nothing else, and cites the guide and step every answer came from. When the docs fall short, it hands the question to you rather than guessing.
It answers from that hub's docs only
Doc is scoped to what that hub holds, so a client is never answered out of another client's documentation. Every answer Doc writes is marked as AI-written.
When it cannot, it opens a ticket
When the docs genuinely don't cover the question, Doc opens a ticket instead of guessing. The ticket lands in your Inbox, and your reply appears in the reader's thread.
It shows you what to document next
A question you had to answer by hand is the strongest signal there is about what to write next. Doc surfaces the gap; the guide is still yours to write.
One account for what usually takes four tools.
Notion and Google Docs
Good places to write, and most people write somewhere before this. What they cannot do is tell you who a document is for, or keep every copy in step once it is handed out.
Scribe, Tango and Loom
Good at capturing a first draft. Docssier keeps the extension for that, and adds what comes after: one library, and a branded hub with an address, for each audience.
Intercom, Help Scout and Zendesk
Help desks with a knowledge base attached, priced per seat for a support team. If you need the whole suite, use one. If you need a knowledge base with a chat in front of it and a ticket when that is not enough, that is this.
Ready to write it once?
Capture a process, publish it as a help center under your own name or a client's, and answer the repeat questions from what you published.