What are Sites?

When a page is the right answer

Some output is produced and consumed by the same person in a minute. Some output is meant to be looked at: figures a leadership meeting works from, a checker a client uses, a reference several staff open during the week.

For that second kind, a page beats a file. It has an address, it is always the current version, and nobody has to be shown where it lives.

What can sit on one

• A dashboard laying out the numbers that matter, in the order they get discussed.
• An artifact, embedded, so staff can set their inputs and get output on the same page.
• A skill, running behind a simple form, for a task anyone should be able to trigger.
• Plain reference content — the agreed method, the checks, the definitions.

Where we use them

A consultancy we work with needed their performance figures in one place, ready before the weekly meeting rather than assembled during it. That is a site: the same page each week, the current numbers, and no version confusion.

Our own practical AI demonstration is a site too — you can open it and try the same kind of tool we build, without installing anything.

The one thing to get right first

Decide who the page is for before it is built. A page that tries to serve the boss, the crew and the client at once usually serves none of them. One audience, the decisions they make, the numbers behind those decisions — in that order.