Crafting a Style Guide for a Multi-Section Archive

A long-running archive site is rarely written by one person. Over the years, volunteers, friends of the project, and occasional guest writers all leave their fingerprints on the text. Some prefer em dashes; others avoid them. One writer splits infinitives without flinching, while another circles every heading in title case. Without a shared reference, the archive drifts.

A multi-section archive is even harder to hold together. Different sections of the same project can serve very different readers. A community-focused section might lean conversational, while a reference section demands a more formal register. A preservation log calls for precision, while a remembrances page calls for warmth. A style guide knits these strands into one recognisable voice.

When that style guide is written down, it stops being an instinct held by a single steward and becomes a tool the whole team can carry. New contributors can read it on their first afternoon. Old hands can return to it whenever a judgement call feels slippery. The archive stops looking like a patchwork and starts reading like one publication.

Setting the Tone and Voice

Tone is the personality that walks into the room before any specific word is read. For a long-lived archive, that personality should feel steady, patient, and quietly curious. It should not shift dramatically between sections, because regular visitors begin to recognise the archive by feel as much as by content.

Reserve the warmest voice for community-focused sections. A piece honouring a contributor's work, or a note about a local gathering in Brisbane or Fremantle, can use first-person reflection and a gentle Australian cadence. "No worries" and other small colloquialisms fit naturally there. Keep them light: a single turn of phrase per paragraph is enough to feel local without becoming a folksy costume.

Reference and historical sections deserve a more measured register. Sentences can be slightly longer, vocabulary more precise, and the tone more clinical. This is where a note from the National Archives of Australia or a transcription from a state library might sit comfortably. The contrast between the two registers is healthy, but the underlying voice, attentive and unhurried, should remain the same.

Headlines, Headings, and Hierarchy

Headings are the bones of an archive. They shape how a visitor scans, how a search engine reads, and how a printout later looks when the screen is gone. Pick one heading style and apply it without exception across every section of the archive.

Decide early whether top-level headings use sentence case or title case, and whether subheadings follow the same rule. Most long-form archives settle on title case for the H1 of an article and sentence case for everything underneath. That combination feels both inviting and orderly. A reader moving from a Sydney-based historical article to a Perth regional report should never feel the typography has changed hands.

Hierarchy must be visible at a glance. Use H1 once per article, H2 for major divisions, and H3 sparingly for sub-points. Reserve bold text inside paragraphs for terms being defined, never for emphasis that should have been a heading. If a heading can stand on its own as a question a reader might ask, it earns its place.

Capitalisation, Punctuation, and Spelling

Australian English is the natural default for a project with local roots. Write colour, organisation, behaviour, centre, and defence rather than the North American spellings. The single biggest visible marker of national voice on a page is often the spelling of these words. Keep them consistent throughout.

Dates follow the day-month-year pattern that Australians are used to reading in newspapers, on television, and in council notices. "5 March 2024" reads more clearly than "March 5, 2024" for the home audience. Times can use the 24-hour format in technical sections, especially where events cross state borders and the AEST-to-AWST difference of two or three hours matters. Otherwise, the 12-hour format with am or pm is friendly enough.

Punctuation has its own small traditions. Use single quotation marks for nested quotations and double for direct speech. Serial commas stay out of running prose unless clarity demands one. Contractions such as "it's" and "we're" are fine in conversational sections and feel forced in archival entries, so let the section guide the choice.

Linking Practices across Sections

Links are the architecture of any archive, and they deserve their own paragraph in any style document. A predictable linking style lets readers build trust: a hyperlink looks the same in section one as it does in section seven. Start by deciding what counts as a link. Bare URLs are forbidden; every link needs a short anchor woven into a living sentence.

Choose anchor text that tells the reader where the journey ends. "Click here" and "read more" tell the reader very little. Instead, weave in a phrase drawn from the surrounding text. The anchor should already describe the destination, so a reader can guess what sits on the next page without clicking through. Predictable wording builds trust, especially for visitors who return to the same archive over many years.

External links deserve extra care. When a story references a piece hosted elsewhere, such as a guide on watermark automation workflow for editorial teams, the anchor should make that destination obvious. Avoid clustering several links into one paragraph; spread them across the piece so the reader's eye can pause and follow each one on its own merits. Broken-link audits belong on a quarterly checklist, especially for an archive that has been quietly publishing for years.

Visual Consistency and Layout

Words are only half of an archive's style. The visual frame around them shapes how seriously a reader takes the content. Pick two typefaces and stick with them: one serif for long-form reading, one sans-serif for navigation and labels. The choice signals taste and saves the eye from constant adjustment.

Colour use should be restrained. A single accent colour for links and section markers keeps the archive from looking like a fair-ground sign. Reserve heavier blocks of colour for cover images or seasonal banners. Captions, where present, sit beneath images in sentence case and follow a fixed pattern: a brief description, then the date or source where known.

Photographs deserve their own conventions. Always credit the contributor, mention the location when it is identifiable, and prefer alt text that describes the subject rather than the file. A black-and-white scan from a Gold Coast historical society, for example, can carry alt text that names the building and the era, giving screen-reader users and search engines the same context.

Maintenance and Stewardship over Time

A style guide is a living artefact, not a plaque on the wall. Schedule a yearly review, perhaps tied to the calendar of a slow month like late winter, when contributors have a little more breathing room. During that review, note which rules have held up and which ones have been quietly ignored.

Version the guide so contributors can refer to "Style Guide 4.2" without confusion. Keep older versions accessible, because the archive itself may one day need to cite how a heading was written in a particular year. New contributors benefit from a one-page summary alongside the full document; the summary handles most day-to-day questions, while the long form sits behind it for rarer cases.

Stewardship is the quiet heart of any long-running project. The guide is a tool, but the practice of caring for the archive is what keeps the publication readable across decades. A patient editor reading the guide before publishing a single line is worth a hundred technical fixes after the fact.

If you maintain a multi-section archive, or you are about to start one, take an afternoon this week to write down the rules you already follow. You will be surprised how much you already know, and how much calmer your future contributors will feel when they can read the answer instead of asking. The preserved materials on this site, including older community articles and reference entries, can serve as a working reference. Anyone wanting to keep up with announcements and updates can read the latest news as it is published, then check back in a few months to see how the archive itself has evolved.