About pages, explained without the jargon
It comes up on almost every project, usually later than it should. Here is about pages without the vocabulary that usually surrounds it.
Writing for the web is largely an editing job: the first draft is always longer than it needs to be. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.
The short version
The about page is often the second most visited. The reasoning matters more than the rule, because the rule has exceptions. Assume whoever inherits this will have half your context and none of your patience.
Why people complicate it
Most of the confusion comes from tooling rather than from the idea itself. There is a version of this that is over-engineered, and it is worth avoiding.
Visitors are checking whether you are real. Small and consistent beats large and occasional here. It is worth deciding this deliberately rather than inheriting whatever the last person set up.
Making it stick
Photos of actual people outperform stock imagery. In practice this is a scheduling problem more than a technical one. It is the sort of thing that looks like polish right up until it costs you an enquiry.
In practice
Content is the part of a project most likely to be underestimated and most likely to delay a launch. Three things worth confirming about about pages before you move on:
- Someone can say what the current setup is without going to look
- Photos of actual people outperform stock imagery — and you know whether that is true here
- There is a way to tell whether the last change to this helped
Worth checking on your own setup before it becomes someone else's problem to fix.