Skip to content

Where to start

Which of these pages you need and how long each takes, what to read if you are only looking something up, the work in front of us, and what else Claude Code can do with the files you already have.

Before this site existed, our documentation lived in three places, the third of them a set of folders holding 106 white papers, technical notes, fact sheets, wall charts and workbooks that went out to customers one at a time by email. Every fact existed in several copies. Updating one did nothing for the others, and a customer had no way to tell which copy was current.

Now there is one site, and one current version of every page on it. When something changes, one request updates every page that mentions it.

Two pages explain how to work in it. The first takes 15 minutes to read; the second adds about half an hour of setting up the workspace, for the people who will be making edits.

If you are only here to look something up, you need neither. Using this site is the short tour of the table of contents, the search box and the Ask the docs assistant, and it is all the reading a reader needs.

Which page to read

If you are Read How long
Only looking something up Using this site 10 minutes
Reviewing or approving documentation How this site works 15 minutes
Making the edits yourself The same page, then Getting started with Claude Code to set up your workspace 15 minutes, then half an hour
Checking which documents have already been submitted Source document library A lookup
Weighing whether this deserves the firm's time Current value and roadmap 10 minutes

Or ask the site which page you need

The Ask the docs assistant sits in the bottom-right corner of every page, including this one. Tell it what you do and let it do the sorting for you: "I'm a sales rep and I'll be correcting product pages. What do I need to know from these setup pages?" Say what your job actually involves and the answer comes back aimed at it, with links to the pages it drew from. Using this site covers what the assistant suits and what it cannot answer.

The work from here

  • More source material is still waiting to go in. Handouts, notes and documents that have never been submitted are sitting in folders, and they move faster when everybody can hand files over themselves instead of routing them through one person. Getting started with Claude Code covers how to do that.
  • Somebody has to read what Claude produced. The pages it wrote or changed need checking against the documents behind them, and the map in the source document library records which page came from which document, which is the quickest way in. Anything that needs fixing goes back through Claude Code like any other change.
  • Meeting transcripts and email can start going in by hand. Claude can pull out whatever belongs in the resource center, and doing it manually before automating anything lets us judge the quality of what comes back.
  • The Ask the docs assistant answers from what the site says, so a question you have already answered on a page does not come back to you by email.

The same work on your own files

Claude read all 106 documents in the source document library and classified them, turning up 5 duplicates filed under different names and 10 superseded editions nobody remembered. That was ordinary file work, just more of it than anyone wants to do by hand. The same applies to what you have sitting in folders now:

  • Finding what has gone stale. Claude compares a document against the current software, or against a newer document, and reports where the two disagree.
  • Consolidating what overlaps. Four overlapping documents become one page that says everything all four said, with the originals kept on file.
  • Changing something everywhere at once. A product name, a phone number or a price that appears in 40 files, corrected in one pass.
  • Keeping one voice across everything. The house style guide lives in the repository, so a proposal, a support reply and a fact sheet all come back sounding like us. Draft it rough and let Claude tidy it.

Proposals on a shared drive, customer correspondence nobody has filed, spreadsheets nobody has reconciled, training material nobody has updated in years: all the same job.

How technical the two pages are

How this site works has no code on it and asks you to install nothing. It explains what the system does and why. Getting started with Claude Code is a checklist of screens and buttons, in the order you work through them.

Neither page asks you to write code. The one skill involved is describing a change clearly in plain English, the same way you brief a colleague.

What you get, and what it asks of you

You get the work back faster. You also get it back complete, because Claude checks every page instead of the ones somebody remembered. That reach is also why it has to be used carefully. Claude can correct 40 files in one pass, and it can put a mistake into 40 files just as quickly and publish it a minute later. There is no bulletproof way to prevent that. The person who asked for the change is the one who catches it, by knowing what they asked for and reading what came back before approving it. That check only works if the reviewer understands what they are looking at.

So read the two pages before you need them. They tell you how to ask for the right thing, how to spot an answer that is wrong, and what you are vouching for when you approve a page a customer will read.

Then keep going past the setup. People who use this a few times a month get individual jobs done faster. People who use it regularly stop doing whole categories of work by hand. Spend the 45 minutes, then bring it something real from your own work: the folder you have been meaning to sort out, the document set that has never been reconciled, the guide you keep rewriting by hand.

Where this is going

Somebody rebuilds a laptop and needs it working again by the afternoon. The installation files for the VPN are somewhere. Pulse Dashboard has to go back on, which means finding the application folder, knowing which server and database to connect to, and how to license that database if it is a new one. Every one of those answers exists, and every one of them exists in somebody's head rather than on a page.

The plan is to grow this site into the firm's resource center, so those answers have somewhere to live.

Deciding whether this is worth the firm's time?

Current value and roadmap is the page that answers it. It sets out what changes when we commit to using this framework fully: we answer customers faster, we get each other unstuck sooner, and the time that frees goes back into the work. It takes 10 minutes to read, and it is the business case rather than the mechanics.

Support & contact

Our team is glad to walk through any of it, including getting your accounts set up.