File a review only under “noise” and its most useful detail—a cassette label, a recording method, a shift in an artist’s practice—may be hard to find later. Publication date and genre can only tell readers so much. A growing music archive needs a few consistent ways into the same body of work, depending on what someone remembers or wants to explore.
Start with the articles, not a new menu
Export or list every published post before changing the site’s structure. Record the title, URL, publication date, article type, primary subject, existing categories, and any broken or ambiguous metadata. A spreadsheet will do. Include drafts only if they are likely to join the archive soon; otherwise they can skew the picture of what readers can actually access.
Sort the list a few ways. Count reviews, interviews, essays, listening guides, and archival notes. Then look for recurring subjects: recording processes, cassette distribution, field recording, documentation of live performances. Some clusters will deserve a place in the archive; others will prove misleading. A category with three posts may be premature, while a broad “artists” category containing half the site tells readers almost nothing.
Before editing, note which URLs must remain stable. Renaming a category is usually less disruptive than changing a post address, though that depends on how the site builds its URLs. Keep working addresses where possible. If one must change, set up a redirect from the old address and test it after publication.
Give each kind of label one job
Categories should describe the main editorial form or subject area, and there should be few enough to browse. Tags can connect narrower ideas across categories. A review of a drone recording and an essay about electroacoustic performance might share a “sustained tone” tag without belonging in the same category. That distinction only works if editors apply it consistently.
A workable division
- Categories: a short, stable set such as Reviews, Interviews, Essays, Listening Guides, and Archive Notes—if those forms genuinely exist on the site.
- Tags: recurring, specific subjects such as field recordings, cassette labels, live documentation, or recording equipment. Use a tag when it connects multiple posts.
- Article metadata: artist names, release titles, formats, and dates kept in clearly identified fields or written consistently in the text. These facts do not all need to become browsing labels.
There is no universal reason to give noise, ambient, and drone separate top-level sections. Some writing crosses those terms; other posts resist them altogether. If genre helps readers use this archive, define how it is assigned and let a post carry more than one relevant tag. Do not assign a genre just to make every article fit a tidy menu.
Write a short internal rule for each label. “Field recordings,” for example, might mean that recorded environmental sound is a substantial subject of the piece, not a passing comparison. Merge near-duplicates such as singular and plural variants, and retire labels that lead to just one unrelated post. If a tag is hard to define in one clear sentence, it may be too vague to maintain.
Build routes that answer different browsing needs
Someone looking for a particular artist is searching differently from someone interested in how tapes circulate or how to listen to a dense live set. Keep the chronological archive, but add a limited number of other entry pages where the material warrants them: an index by article type, a subject guide, or an alphabetical artist index if artist-focused posts are numerous.
Give those pages brief descriptions, not just grids of titles. A page on field recording could separate reviews of recordings from pieces about recording practice. A guide to live music could offer a festival listening piece as a starting point while identifying it as a guide, not a performance review. Readers should not have to open six tabs to work out what each post contains.
Do not publish sparse hub pages just to make the menu look complete. If a topic has only two articles, a tag page may be enough. Once it has grown into a substantial group with a clear editorial connection, a page with selected entry points makes more sense. Such pages need upkeep, too: an index that quietly omits newer work can be less useful than a plain chronological list.
Make archive entries legible on their own
An archive card or search result should tell readers more than the title. Show the article type, a short description, and the publication date. For time-sensitive pieces, show an update date separately when the article has materially changed. A review written at the time of a release should not look like a new assessment because someone corrected a spelling error years later.
Titles need context when several posts concern the same artist. If a short, evocative headline conceals whether the piece is an interview, a review, or an analysis of a document, say so in the excerpt or a visible label. On smaller screens, put the distinguishing words early enough that they will not be cut off.
Check the archive without relying on thumbnails. Cover art may be unavailable, hard to credit, or visually similar across releases. Text labels should still distinguish an artist profile from a close reading of an unidentified file. Search results also need useful descriptions, not the same generic opening sentence pulled from every post.
Clean the old archive in controlled passes
Reclassifying everything at once makes mistakes hard to spot. Start with a small batch: frequently visited pages and posts that plainly sit in the wrong category. Keep a record of old and new labels so you can trace apparent gaps. After each pass, check that public category pages still show sensible results.
- Identify duplicate and unclear labels without deleting them yet.
- Choose preferred terms and write one-line definitions for contributors.
- Reassign a test batch, then inspect the resulting archive pages.
- Apply the rules to the remaining posts, flagging uncertain cases for editorial review.
- Remove unused labels only after confirming that no navigation or saved index depends on them.
Older pieces may lack reliable release details. Do not fill the gaps by guessing from a filename, an upload date, or a later reissue. Mark the information as unverified in editorial records, and keep the public description precise about what is known. A better-organized archive should make uncertain evidence easier to recognize, not turn it into a false catalog entry.
Test the paths after every change
Try realistic searches on the finished site: an artist’s name, a format, a recording technique, and a phrase from a title. Browse from a category page to a post and back. Check pagination, mobile labels, empty results, and whether posts appear under tags that genuinely describe them. Ask someone unfamiliar with the labels to find a review and a listening guide without telling them which menu item to choose.
Make classification part of the publishing checklist so the archive stays usable. For each new post, choose one primary category, select only established tags that apply, and propose a new tag only if a second post would plausibly use it. Once a month, inspect tags used by just one article. The newest one is a good place to catch a spelling variant before it spreads.