Before announcing a new music journal, open a release page on your phone with the sound off. Can you find the artist, title, format and label without pressing play? The player might fail, or a reader might be unable to listen. The written record still has to make sense. This quick test catches a common launch problem: a site can look finished while the information readers came for remains hard to find.
Decide what the site must do
Write down what the website needs to do before settling its appearance. An independent publication covering noise, ambient music and small-run releases might need to help readers find essays, present uncertain release details honestly and give artists a way to request corrections. A cassette label has different priorities: its catalog needs clear format and availability information. An event archive needs dates, venues and a record of what happened.
- List the essential page types: home, article or release entry, about, contact and any catalog or archive index.
- Choose one primary route into older work: a clear archive, useful categories or a dependable search function.
- Assign an owner: name who handles editorial changes, technical maintenance and incoming messages, even if one person does all three.
Keep the launch small enough to test. A modest archive with consistent entries is more useful than dozens of thin pages made to fill a menu. You can add sections later; removing confusing navigation once readers rely on it is harder.
Prepare content as evidence, not decoration
Check every visible page
Read the home page, about page, contact instructions and a representative article in the published design. Check headings, dates, credits and punctuation after pasting text into the site. Make sure navigation labels match their destinations. An “Archive” should not show only recent posts, and a “Contact” page should not bury its sole address in an image.
For release entries, agree on a minimum set of fields: artist or project name, title, format and label when known. Keep the sources for uncertain details in your working notes. An empty template field is no reason to turn a guess about a cassette’s year or edition size into fact. If documentation conflicts, say so in the entry. Keep the review’s publication date distinct from the recording’s release date.
Check image and audio permissions before uploading. Owning a cassette, sleeve scan or recording does not necessarily give you permission to reproduce its artwork or host its audio. Record permissions and agreed credit wording. If an entry uses an embed from another service, its text should remain useful when the embed disappears.
Make a short prepublication sample
Do more than proofread pages one at a time. Follow a few reader routes: an essay to an artist page, a category index to an older review, a search result back to the archive. Fix empty categories, broken references and pages that normal navigation cannot reach. Write internal link text that names the destination rather than saying “more.”
Test access and presentation
Use a keyboard to reach the menu, search, audio controls and contact form. Can you see where focus has moved? Check heading order and give informative images concise alternative text; decorative textures do not need descriptions that repeat the prose. If speech or other essential information appears only in audio, provide a transcript or substantial written description. Readers may not be able, or willing, to press play.
Try a narrow phone screen and a larger desktop display. Watch for clipped captions, tiny track lists, overlapping menus and players that spill beyond the page. Check contrast, especially where pale text sits over sleeve art. Disable images once to see whether titles and navigation still make sense.
Speed matters when a slow page interrupts reading. Resize oversized artwork, use thumbnails instead of full-resolution scans in listings, and test a page with several embeds on an ordinary mobile connection. Load an article, then open it in a fresh browser session: does the text appear promptly, without waiting for audio or animation? If the site runs on WordPress and an unexpected background request is slowing pages, the journal’s guide to how admin-ajax.php slows a DIY music site addresses that particular cause. It will not explain every slow page.
Confirm the machinery before changing the domain
- Secure access. Use distinct strong passwords, enable multi-factor authentication where available, and give contributors only the permissions they need. Remove temporary setup accounts.
- Make a recoverable backup. Save site files and, where applicable, the database. Know who can restore them. Test a restore on a nonpublic copy; an untested backup is not much protection.
- Check the domain and HTTPS. Confirm that the intended domain loads securely, alternate versions redirect to the preferred address, and embedded resources do not cause browser security warnings.
- Test delivery. Send a message through each contact form to an address you can check. Confirm it arrives, errors are understandable and submitted details do not appear publicly.
- Inspect discoverability settings. Remove any staging-site block on indexing if the public site should be discoverable. Check page titles and descriptions, the sitemap if one is generated, and whether private drafts remain private.
Handle privacy in the same pass. If the site uses analytics, embeds, mailing-list forms or cookies, identify what data each collects and publish an accurate policy. Do not copy a generic notice listing services you do not use. Keep form submissions only as long as there is a reason to retain them.
Run the launch from outside the editor
Editors know where everything is because they built the site. Open the public domain in a private browser window and ask someone unfamiliar with it to find a specific older article, identify its author and send a correction. Give them the task, not directions. Watch where they hesitate. A misleading menu label may be the problem, not the whole design.
Check important pages after the domain goes live, not just on staging. Follow a link from a message or social post to make sure it lands on the intended page. Look for old preview addresses in image paths, canonical settings and shared page previews. If old URLs are changing, set up redirects and test several individual articles, not only the home page.
Keep a brief launch log: when the domain changed, where the backup lives, which defects remain and who can fix them. Deal first with problems that block readers, such as a missing archive link or an inaccessible contact form. A small spacing inconsistency can wait. Check again after the first visitors arrive; form failures, broken links and server errors may only become apparent then.
Before sending the announcement, copy the URL of an older cassette review and open it in a private window on your phone. Without going through the home page, find its title, credits and correction contact. Note the first place you get stuck and fix it.