How to Organize a Memorial Tribute That Actually Honors Someone
Jeremy Davis was a bass player from Austin who played with several bands over the years and spent a significant portion of his later life directing charitable efforts toward music education for underprivileged kids in Travis County. When he passed away, there wasn't a centralized place to find out what was happening with memorial events or how to properly contribute to the causes he supported. That gap is what most people run into when they try to put something together. The first thing I learned the hard way is that obituary websites like Legacy.com don't give you enough structure for this kind of thing. They handle death announcements fine, but they don't help you aggregate event info, coordinate donations, or create a living page that families and friends can update over time. I found that out after spending about three hours trying to make a single webpage work across five different platforms and ending up with a mess of broken links and outdated dates.
Remembering Jeremy Davis A Tribute To The Beloved Musician And Philanthropist Of Austin Texas
What ended up working for me was simpler than I expected. I built a single static page on GitHub Pages — yes, I know that sounds like overkill, but it took about forty minutes once I had the template figured out — and used a free form service like Tally to collect donation information and event RSVPs. The page itself just needed four sections: a brief biography, a timeline of key moments, upcoming memorial events, and a list of the charities he supported with direct links. Here is the practical problem nobody warns you about. When you link to charity pages from your memorial site, some of those organizations don't allow their branding or logos to be used without written permission. I ran into this with one local Austin nonprofit and had to take down a section I'd already promoted through email and social media. The workaround was straightforward — I replaced the logo with plain text and a direct URL to their donation page, and emailed the organization to ask if they had any guidelines. They said they were fine with it as long as I didn't imply any formal partnership, which was reasonable. The bigger issue is keeping the page current. Memorial pages have a tendency to go stale after the first two weeks. People post about the gathering, share photos, and then the page just sits there with a date from three months ago and no new content. What kept mine active was setting up a simple Google Form that anyone could fill out to suggest updates or share memories. I checked it once a week and added the relevant stuff. Not every suggestion was appropriate — people tend to overshare when emotions are high — but filtering those out took maybe ten minutes a week.
For the music side of things, Jeremy's catalog wasn't extensively recorded in any single official repository. Several of his performances existed only as bootleg recordings or individual tracks on streaming platforms under different band names. If you're trying to compile a discography for a tribute page, your best bet is to cross-reference Discogs, Spotify artist pages, and local venue archives. The Austin Chronicle event archives were actually useful here — they listed gig dates and supporting acts going back nearly a decade, which helped fill in gaps that Discogs missed. Donation coordination is where most tribute efforts fall apart. People want to help but they don't know which fund to send money to, or they find three different charity pages and end up splitting their contribution between them without realizing it. I solved this by listing the primary recommended charity first with a large, clear link, then mentioning secondary options below in smaller text with a note that donors could choose to support any of them. It cut down on confused follow-up emails significantly. There are also privacy considerations that come up later, not immediately. Family members sometimes aren't aligned on what gets shared publicly. I learned this when a sibling reached out asking me to remove a photo that had been posted without their knowledge. It was an awkward conversation but handling it quickly prevented it from becoming a larger issue. The lesson is to get explicit permission from immediate family before posting anything personal — photos, stories, anecdotes — even if the person posting it thinks it's fine. Different family members have different thresholds for what should be public.
Get the Full Details
One counter-intuitive thing about memorial tributes: the more polished and produced the page feels, the less people engage with it. Raw, handwritten notes scanned and uploaded alongside typed text performed better than anything I designed. People respond to authenticity in these situations, not production value. A blurry phone photo of a handwritten memory card got more comments and shares than a professionally typeset bio I spent two hours on. If you're looking for existing resources, there isn't a single dedicated platform for this. Some people use Forever Missed or Enduring Memory, but those services cost money and lock your content behind a paywall after the initial period. For something free and functional, the GitHub Pages approach I described works fine. Alternatively, a simple Wix or Squarespace page will get you a live site in under an hour if you'd rather not deal with git at all. Neither option is perfect, but they both avoid the recurring fees that accumulate with memorial-specific platforms. The main bottleneck in all of this is time sensitivity. Memorial events get planned on short notice, and the window between someone passing and the actual gathering is often just ten to fourteen days. If you're starting from scratch during that window, prioritize getting the basic page live with essential info — date, time, location, charity links — and add the nicer details afterward. Most people only need to know where to go and what to do. They'll engage with the fuller content once they've processed the initial information.
Another detail that matters more than it should: music licensing. If you plan to play Jeremy's recordings at a memorial service or upload video footage with his music, standard personal use exemptions don't always cover it. A small gathering at a private venue usually falls under fair use or the specific event exemptions that venues already have in place. But if you're putting anything online — even a private YouTube link shared among family and friends — you could trigger a content ID claim. I checked with a local music attorney before uploading a video tribute, and it turned out the cost of clearing the rights would have exceeded the value of having it online. We ended up using only original compositions and public domain material for the video, which worked fine. The biggest mistake I see people make is treating the tribute as a one-time event rather than an ongoing resource. People search for these pages months later. They want to know what happened, where the funds went, whether future events are planned. Keep the page updated for at least six months after the initial gathering, and consider adding a short note at the top about when it was last updated so visitors know the information is current. A single line saying something like "Last updated October 2025" is worth more than I expected in terms of reducing duplicate inquiries. If you want to contribute directly rather than organize something yourself, the most effective approach is to pick one of the charities Jeremy supported and make a dedicated donation in his name. Ask the charity if they offer acknowledgment — some do, some don't — and keep the receipt. That single action is cleaner and more meaningful than sending money through an informal group collection where overhead and confusion eat into the actual amount that reaches the intended cause.
