“Finnish thrash metal archive” tells visitors what a site is about, but not what they will find there. Release histories? Concert documentation? Interviews? An About page should settle that question early, then explain who does the work, where its limits lie, and how readers can get in touch.
Start with the blog’s actual scope
Say what the blog covers in plain language. For a small archive, that might be independent Finnish thrash-metal releases and local concert activity from the late 2000s through the mid-2010s. Earlier influences and later reissues may belong in the story, but as context rather than an unannounced expansion of the period. Clear boundaries help explain why one band has an entry and another does not.
Be equally clear about the kind of writing readers will find. “Documenting release histories, concert activity, and the sound of the scene” promises something different from “reviewing every new metal record.” A blog can do both, but its About page should describe the work that exists now, not an abandoned plan or an unwritten section.
An opening might read: “This independent blog documents Finnish thrash-metal bands, releases, and live activity, with particular attention to the late 2000s and early 2010s. Entries bring together verifiable release details and contemporary context for listeners and collectors.” It names the subject, period, method, and audience without pretending to cover everything.
Explain who maintains it—and what that means
Readers do not need a long autobiography. They do need to know whether this is one person’s research project, a group archive, or an official band publication. If one editor runs the site, say so. If contributors provide photographs or memories, explain how those contributions are credited and checked.
Use a name or consistent byline if possible. When privacy rules out a full legal name, a stable editorial name and a working contact address still give readers someone accountable to approach. Skip claims like “the definitive authority on Finnish thrash.” Relevant experience is more informative: collecting physical releases, attending gigs, interviewing participants, or comparing edition details—if those things are true.
Make the site’s relationship to the bands clear, too. Writing about a band does not mean the blog speaks for it. If the archive is unaffiliated, say so. If a contributor is a musician whose work appears on the site, disclose that connection where it matters rather than claiming blanket neutrality.
Describe how entries are researched
The About page need not be a research manual, but it should tell readers what counts as evidence. Does the editor check physical copies, label materials, band statements, dated flyers, or contemporary coverage? What happens when sources disagree?
For instance: “Release credits are checked against available physical editions and contemporary materials where possible. Unconfirmed dates are marked as uncertain rather than presented as fact.” A collector can do more with that than with a promise of “accurate content.” It also acknowledges a familiar problem: not every demo is accessible, and a local show may have left no reliable date or set list.
Separate documentation from interpretation. A pressing’s track list can be checked; a description of its guitar tone as indebted to classic thrash is a critical judgment. Both belong on the site, but they should not be confused. Label first-person accounts as recollections, and check dates and billing against records where possible. A vivid memory alone is not a confirmed concert history.
State the limits without apologizing for them
A small blog does not have to promise coverage of everything. Gaps may reflect the available evidence, the editor’s time, or the site’s chosen focus—not the importance of omitted musicians or releases. Underground recordings and short-lived venues often leave uneven paper trails. A brief note about that uncertainty helps readers understand what an absence does, and does not, mean.
Give visitors a clear route through the site
Once readers understand the project, show them where to go. Name the material they can actually find: band histories, release entries, concert documentation, or essays on sound and community. If the site has stable section pages, point to them by descriptive names. “Explore the archive” is less useful than a small map of what is organized where.
The About page explains the publication’s purpose and approach; category pages sort individual posts. There is no need to list every band or record in the About text. Keep the map short and update it when the site changes. An empty discography section or a dead heading is worse than a modest description that matches what visitors can open.
Make contact useful for both sides
For an archive, a way to report corrections matters more than a vague invitation to get in touch. Ask readers to identify the page and the disputed detail, and to include a scan, photograph, or contemporary reference if they have one. They should not have to send private material just to flag a possible error. A working email address or accessible contact form is enough; a personal phone number is seldom necessary.
If corrections and submissions are handled differently, explain the distinction. A musician offering a flyer should know whether it might be published, credited, or kept only as a research reference. Sending material does not automatically grant permission to publish it. Nor does information about a recording mean the blog will host audio files or provide unauthorized copies. Clear boundaries protect the contributor and the archive.
Set a realistic expectation for replies. An independently maintained site may not be able to investigate every message promptly, but it can acknowledge useful evidence and correct a verified mistake.
Keep disclosures proportional to the site
Readers should be able to spot relationships that might affect coverage. If the blog receives review copies, accepts paid placements, sells merchandise, or uses affiliate links, describe the arrangement plainly and point to any fuller disclosure on the site. There is no reason to invent a funding statement when none applies. There is also no reason to call a record a purchase if it was sent for review.
Be just as careful with permissions. The About page can say that photographs, flyer scans, and artwork remain with their respective rights holders and invite questions about attribution or use. It should not suggest that every historical image is free to reuse. Say material is displayed by permission only when that permission has been obtained.
Arrange the page for a quick first reading
Put the information most visitors need first. For a small blog, this order works:
- Purpose: the subject, period, and kind of coverage.
- Editor: who maintains the site and whether it is independent.
- Method: the evidence behind factual entries and how uncertainty is marked.
- Navigation: the main types of material available.
- Contact: how to send corrections or propose material, including permission boundaries.
- Disclosures: relevant funding, review-copy, or contributor relationships.
A very small site may not need a heading for each item. Readers should still be able to find them without working through a personal history first. Short paragraphs and descriptive headings help on a phone, especially when someone has come looking for contact details.
The page should also look at home on the site. If historical entries use restrained imagery and legible type, the About page needs neither a dramatic band photograph nor an oversized manifesto. For the wider design question, see the archive’s guide to visual identity for a Finnish thrash-metal archive.
Revise it when the blog changes
An About page can be inaccurate without looking old. A contributor joins, review submissions close, or the focus narrows from general metal coverage to a particular scene and period. Recheck the page when those decisions change. Make sure the contact method still works and every section it mentions is available to visitors.
Before publishing an update, compare each promise with the site itself. If the page claims to publish interviews but none exist, remove the claim rather than advertising a future possibility as current work. If it invites corrections, test the listed contact channel. That small detail may be the first thing a reader needs when they spot a misidentified release credit.
