Docssier
    Capture

    The screenshot files itself into the step.

    The slow part of documentation was never 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

    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.

    Branded hubs

    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.

    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 is theirs.

    Reader views

    Every guide reads three ways.

    One guide, published once. The reader picks the format that suits how they are reading it — nothing is written twice, and nothing is converted.

    Article

    The whole guide as one scrolling page, steps and screenshots in order. Easy to skim, easy to search, easy to link to a single step.

    Slides

    One step at a time, full width, with the reader moving forward at their own pace. Useful when someone is following along on a second screen.

    Movie

    The steps advance on their own, so the process plays through from start to finish. It is a view of the same steps that plays itself, not a video file to download.

    Import

    Start from what you already have.

    Most people arrive with documentation somewhere else. Bring it in, look it over, and keep the links you have already given out.

    Scribe share linksScribe PagesHelp ScoutA Notion exportA sitemapA live page URLWord (DOCX)MarkdownCSVZIP

    Bring it in from where it is

    Import from Scribe share links and Scribe Pages, Help Scout, a Notion export, a sitemap, a live web page, Word, Markdown, CSV, or a ZIP.

    A tidy pass cleans it up

    An AI tidy pass tidies rough or imported docs and restructures them, so what arrives reads like something you wrote rather than something you pasted.

    Your old links keep working

    An old-links step maps your previous URLs to the new ones, so links you have already handed out, bookmarked, or emailed still land in the right place after you move.

    You review before anything is saved

    Everything is shown to you first. Nothing is saved to your library until you have looked at it and accepted it.

    Shared library

    Correct the guide, not the copies of the guide.

    Documentation goes wrong in a specific way: the process changes, and the guide is now in four places — the help center, an SOP that walks through it, a folder someone exported it into, and the head of the person who wrote it. Three of the four are wrong by lunchtime.

    In Docssier there is one guide. Publishing it to a help center does not duplicate it, and embedding it in an SOP does not duplicate it either — both point at the same guide. Correct it once and everything holding it is correct, with no export, no sync, and no version to reconcile.

    You write it once, and there is only ever one of it.

    SOPs

    A procedure that stays current on its own.

    An SOP 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.

    It embeds guides, it doesn't copy them

    An SOP points at the guides it depends on. Change a guide once and every SOP that embeds it stays current — nothing to re-paste, nothing to reconcile.

    Written for the person running the work

    An SOP holds the sections meant for the person running the work, around the guides the person doing it follows step by step.

    Doc AI

    If you didn't write it, Doc won't say it.

    Doc answers strictly from that hub's published docs — the guides and SOPs you put there, and nothing else. Not the internet, not another hub, not its own earlier answers.

    Every answer is cited

    Each answer names the guide and step it came from, so the reader can open the source and check it.

    When it can't, 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.

    Clearly marked as AI-written

    Anything Doc wrote is clearly labeled AI-written, so a reader always knows where the answer came from.

    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.