A release date, a lineup change and a description of the guitar tone answer different questions. Give them separate places in a post about a Finnish thrash band, and readers can follow the history without confusing documented facts with the writer’s interpretation.
That distinction matters in an underground music archive. One reader may be identifying a demo; another may be tracing a venue, comparing pressings or trying to understand how a band sounded live. Details should be easy to find without turning the post into a bare catalog entry. The right structure depends on the material, not on a template used for every band, show and release.
Start with the question the post can answer
Before drafting headings, write a one-sentence working answer to the central question. For a release article, it might be: “This recording shows how the band’s arrangement and production differed from its earlier material.” For a concert-history article: “The surviving documents establish where the band was advertised to play, but they do not establish the full setlist.” The sentence need not appear in the finished piece. It keeps the draft from wandering into every available anecdote.
Sort your notes into three groups: facts readers need up front, evidence that supports the main point, and useful context that can wait. A date printed on a sleeve may belong near the start of a release article. A comparison with another local group can come after the description of the music. A later reissue might need only a short section near the end.
This exercise can expose two posts competing for space. A band biography belongs in a close reading of an EP if it explains the EP. If both subjects require full chronologies, they may be better as separate pieces. No arrangement of headings will fix a question that is too broad.
Choose a shape that fits the evidence
Music-history posts need different structures for different questions. Pick a main shape before arranging individual paragraphs, then borrow from another where the evidence calls for it.
A chronology for developments over time
Use chronology when the order of events explains a change: rehearsal recordings giving way to a self-released demo, shifts in personnel, or performances that brought a band to a wider audience. Start at the earliest relevant point, which may not be the band’s formation. In a post about touring, an early local show may tell readers more than a childhood influence.
Give each period a purpose. “Early recordings,” “A change in the live set” and “The later release” tell readers what changed; year headings tell them only when to look. Keep the event separate from the evidence for it, too. A poster printed before a show documents an advertised bill, not proof that every listed act performed.
Do not give every dated scrap equal space. A minor flyer may warrant a sentence, while the release under examination needs several paragraphs. Group routine developments, then slow down where the record supports an explanation.
A profile for one band, venue or release
A profile builds a picture of one subject. For a release, that might mean identification and format first, followed by recording context, sound, distribution and reception. A venue profile could begin with location and scale, then examine documented bills and what surviving posters or photographs show.
Identify the subject early. If two editions have different artwork or track orders, say which one you are discussing before comparing them. A compact facts list or table helps when distinctions are stable and well documented; prose is better for explaining their significance. An uncertain detail does not become certain because it fits neatly in a table.
A comparison for a specific difference
Compare recordings, lineups or performances when the contrast answers a question neither item can answer alone. Establish the basis first: perhaps the same song appears on a demo and a later release. Then examine both versions against the same points of reference, such as tempo, arrangement, vocal placement and recording texture. Do not describe one at length and dismiss the other in a sentence.
Keep the claim within the evidence. A rougher guitar tone on one recording does not show that an entire local scene preferred that sound. Two available recordings support a comparison of those recordings; a claim about the wider scene needs more sources.
A question-led structure for incomplete records
Patchy documentation may be easiest to present as a set of questions: What is confirmed about the event? Which sources disagree? What remains unknown? Establish the firm details first, address conflicting dates or uncertain credits next, and close by stating what the available record cannot settle. Fragmentary evidence need not be forced into a continuous story.
There is no need to build suspense around a missing fact. If no setlist has survived, say so. The point is to show what the archive supports, not to hint at a revelation it cannot provide.
Make headings useful outside the full reading path
Readers may arrive at a section through a search result or return later for a single detail. Make headings intelligible on their own. “Recording and production” is more useful than “The next step”; “What the poster confirms” is more precise than “A mystery remains.”
Use h2 headings for the main stages and h3 headings for subdivisions. Keep parallel sections at the same level. If the h2 sections cover early releases, live work and later releases, one concert should not become an h2 simply because it has a striking photograph.
Headings should promise no more than the evidence delivers. “European tour dates” misleads if the section contains one confirmed overseas performance and a mention of proposed dates. “Documented performances outside Finland” is more accurate.
Read the headings alone during editing. A jump from a first demo to a later festival appearance may call for a section on the intervening period—or a sentence acknowledging that the archive is sparse. Do not fill the gap with assumed activity.
Keep each paragraph on one job
A paragraph can identify a source, describe a sound, explain a change or qualify a claim. When it tries to do all four, readers can lose track of which statements come from documents and which come from listening.
One useful pattern is claim, evidence, limit. State the point, give the detail behind it, then mark any important boundary: “The later recording places the vocals more prominently. The voice is easier to distinguish from the guitars in the opening verse. That contrast describes the available recordings, not necessarily the band’s live mix.” The sentences need not always follow that order, but the distinction between observation and inference should remain clear.
Transitions work best when they explain a connection. “The recording changed, but the surviving posters show continuity in the live repertoire” links two kinds of evidence. “Another interesting aspect” does not. If there is no useful connection, a new heading may be better than a forced transition.
Use lists and tables for retrieval, prose for interpretation
A short list helps when readers need to pick out parallel details. In a post about a physical release, a labeled list could identify:
- the edition or format under discussion;
- the credits as printed on that edition;
- the tracks relevant to the comparison;
- any catalog or sleeve detail needed to distinguish versions.
Explain the significance in the surrounding prose. A track list cannot tell readers why a song changed between releases. Nor should a list combine printed credits with later recollections without identifying the different sources.
Tables help when the same fields need to be compared across a few items. Two editions, for example, might be set side by side by format, artwork and track order. Explain qualified entries in a nearby sentence, particularly if a sleeve and a contemporary advertisement give different dates. If most cells need long notes, prose will be easier to read, especially on a narrow screen.
Not every section needs a checklist. Lists make details easy to retrieve; connected sentences explain how a band’s sound developed.
Place source limits beside the claims they affect
Do not save every uncertainty for a note at the bottom. If a show date comes from an advertised bill rather than a confirmed performance record, say so where the date appears. Otherwise readers may have to revise their understanding at the end.
Small choices in wording can identify the source without interrupting the account. “The sleeve credits” tells readers what the release says. “A contemporary poster advertises” describes a planned event. “On the recording, the bass is difficult to distinguish” marks a listening observation. Each phrasing makes the basis of the claim visible.
A separate source note still helps when documents disagree or editions are hard to identify. Keep it focused on the post’s question. A release profile needs enough source discussion to make its claims clear; a full treatment of how to evaluate evidence belongs elsewhere.
Let images support the section they appear in
Place a sleeve photograph near the discussion of its credits or design, and a concert flyer beside the passage explaining what it documents. Readers should be able to connect the image to the claim, while the prose should still make sense if the image does not load.
Alt text should briefly describe the useful visible content. If a handwritten date on a flyer matters, mention it rather than repeating an atmospheric caption. Do not leave a date, lineup or credit in the image alone; state essential details in the article text so readers can check them in context.
Consistent visual choices cannot repair muddled editorial order. A post may use restrained images and still be difficult to follow if every section mixes release identification, sound analysis and later reception. The archive’s [visual identity for a Finnish thrash metal archive](/consistent-visual-branding-finnish-thrash-archive/) concerns the publication’s appearance; post structure guides readers through an individual account.
Revise by following three reading paths
Test the draft in three ways. First, scan the title and headings: do they convey the scope and sequence without promising unsupported facts? Next, read only the first sentence of each paragraph to see whether the account moves forward or keeps restarting. Finally, look for details a returning reader might need—a release format, show date, personnel credit or explanation of uncertainty. Each should sit under a heading where someone would expect to find it.
On the last pass, remove headings that introduce only a sentence or two unless they serve a real retrieval need. Split paragraphs when the source type changes without warning. Check that comparisons apply the same criteria to both sides and that chronological sections do not treat announced events as confirmed performances.
For a post comparing two editions of an EP, a workable outline is “Which editions are being compared,” “Differences visible on the copies,” “Differences heard on the recordings” and “What remains uncertain.” Start with format and identification; then place each claim beside the copy, recording or document that supports it.
