A release profile needs room to identify the edition under discussion. A concert account needs a venue, a date, and evidence that the show took place. Start both from a blank page, and those details are easy to miss. A reusable post template can keep them in view without making every piece of Finnish thrash history follow the same outline.
The distinction is between a template and a finished post. The template records recurring decisions: what to collect, where to note uncertainty, and what to check before publication. The post supplies the evidence, narrative, and judgment. Used as a form to fill in mechanically, a template produces repetitive articles. Used as a working aid, it helps a writer see what is missing.
Start with the kinds of posts you actually publish
Before choosing headings, sort a handful of existing drafts by what they do. An archive of Finnish thrash from the late 2000s through the mid-2010s might cover releases, band histories, concerts, interviews, and local scenes. Those posts share some requirements, but a track listing that helps identify a release edition has no automatic place in a festival report.
Look for information that recurs across the drafts:
- Subject and scope: the band, recording, event, or question, and the period covered.
- Identification: names, locations, dates, and edition details that distinguish the subject from similar ones.
- Evidence: the source of consequential claims and anything still unverified.
- Context: the local or musical connections that help explain the facts.
- Media: photographs or artwork, permission status, credits, and descriptive text.
- Maintenance: information that may need updating or correcting.
That inventory becomes the template’s foundation. It saves you from rediscovering the same editorial decisions with every draft. Keep questions specific to one kind of post in separate modules, rather than crowding the master with every field you might someday need.
Build a small common core
Put internal working fields at the top of the master, followed by prompts for the article itself. The working notes guide reporting; they should not appear in the published piece as empty headings.
Working fields
Record a working title, post type, purpose, scope, and status. The purpose should say what this post establishes. “Profiles a demo” gives little direction. “Distinguishes the original demo from a later reissue and describes what can be heard on the original recording” gives the writer a way to decide what belongs.
Add a source ledger with three columns: claim, supporting material, and confidence or outstanding question. A sleeve may establish a title and printed credits; a dated flyer may establish that a band was advertised for a show. Neither proves who played that night. Noting the difference while drafting keeps a reasonable inference from turning into a stated fact.
Use another field for media permission and provenance. “Band photo received by email” is not enough: record who sent it, what use they authorized, and whether the photographer is identified. Leave the field empty if the post needs no image.
Reader-facing building blocks
Write prompts, not stock prose. For the opening: “State the most useful verified detail or distinction about this subject.” For context: “What must a listener know to place this release or event in its local setting?” Both give direction without making every article start alike.
The common core might cover an opening, identification and context, the main account or analysis, and a note on meaningful uncertainties when needed. These describe jobs the prose must do, not headings it must display. A short post might handle them in a few paragraphs; a longer history may need subheadings.
Add modules for distinct post types
Keep the common core small and copy only the relevant module into each new draft. That is easier to use than a single document full of empty sections, and it keeps the published article from inheriting headings it does not need.
Release profile module
Record the title, artist, format, label or verified self-release status, and the exact edition examined. Distinguish what is printed on the item from later descriptions. When writing about the sound, describe something a listener can assess—such as how prominent the guitar is relative to the drums—instead of treating promotional copy as evidence. Specify whether you listened to the original recording, a reissue, or a digital version.
Concert or festival module
Record the advertised date, venue, acts, and sources for each. Then ask what the evidence actually establishes. A ticket, flyer, set list, photograph, firsthand account, and contemporary review answer different questions. If the surviving material shows only that a concert was advertised, do not write about the performance as though it were documented.
Band-history module
Keep a dated working timeline of membership, releases, and documented appearances, but do not assume the article should reproduce it as a list. The timeline may show that the better story follows a lineup change or a run of independent recordings. Publish the chronology that serves the piece, and flag disputed dates instead of smoothing over gaps.
No module should become the default for every post. A venue history may call for an account of its local connections; an interview needs clear attribution for recollections. Add a module when that kind of post recurs and brings a recurring research need.
Make the template easy to use while drafting
Store the master where the archive writes: in a document, a content-management draft, or a plain-text file. Label internal prompts clearly. Duplicate the master for each post rather than editing it, and name the new draft so nobody mistakes the blank template for work in progress.
Keep copied prompts brief. “Source for date” is easier to scan mid-draft than a paragraph on research standards. If a prompt needs explanation, put it in the master’s guidance notes. The draft should make decisions easier, not give the writer more text to sift through.
Mark required checks separately from optional sections. A consequential date needs source support. A discussion of cover art is optional, even in a release profile. That distinction stops a blank section from looking like a failure and keeps verification from being treated as a matter of style.
Test it against a real draft
A tidy blank template tells you little about how it works. Copy it into a forthcoming post and draft a real subject. Notice which prompts you ignore, which ones you add, and where you have to move material to make the article read naturally. Those are the places to revise.
A self-released recording, for example, may expose a problem with a field labeled “release date.” The surviving sleeve might support a year but not the day the recording became available. “Date as stated and basis for it” asks a more useful question without adding a long section.
Try a second post of a different type before settling the common core. If the release profile works but a concert account needs extensive rearranging, the concert module may be the problem. One unusual article is not a reason to rebuild the whole system.
Protect variation and accuracy
Standardize how evidence is handled, not how every story sounds. Let the strongest verified detail lead. A piece on an obscure compilation contribution might open with the recording; one on a disputed show date might open with the conflicting documents. Both can rely on the same source ledger and media checks out of sight.
Make room to state the limits of the record. If all that survives is a flyer, say there is no account of the performance rather than inventing the room’s atmosphere. If credits differ between editions, identify the edition behind each credit. A prompt for “limits of available evidence” helps catch these issues without imposing a disclaimer on every post.
Be just as selective with images. A photograph should clarify the subject, not fill a preset slot. If concert photographs are part of the archive’s workflow, the separate guide to organizing concert photos for a small-scene music archive covers how to preserve their context. In the post template, record the chosen image’s identity, permission, credit, and relevance before placing it.
Maintain one master and revise it sparingly
Date the master and keep a short record of substantive changes. Otherwise, writers may copy different versions without knowing why their drafts ask for different information. After several posts, look at prompts that are routinely deleted, fields writers keep adding, and factual mistakes a better prompt might have caught.
One unusual article does not justify a new field. If several release profiles leave the basis for a date unclear, revise the release module. If a single complicated reissue calls for a matrix-number comparison, handle it in that draft.
For the next release profile, duplicate the master and fill in three working fields before writing: the exact edition examined, the evidence for its stated date, and one claim the available material cannot yet support. If those answers change what you can responsibly say about the record, the template is doing its job.
