I am moving forward with the creation of a WordPress theme/plugin that will help me to archive all of the music that my family and I have created over the years. I figure we have 1,000+ mp3s to store between us.
Figuring out a good way to organize the data is one of the big challenges, as we will want to be able to easily find what we are looking for. With that in mind, I created a custom post type for songs that will have the following custom taxonomies:
- Artist/Band Name
- Album Title that the song is on
- Musicians who play on the song
- Release Year
- Instruments on the song
I haven’t quite thought this through, so I am keeping my options open. Therefore, I installed a WordPress multisite installation + BuddyPress. I don’t know if I will use either of those features, but it is nice to know that I can fall back on those technologies if needed. Therefore, I am using a child theme of BuddyPress. So far, I have only slightly edited the single.php template.
So, right now, after a few hours of work, I have a working BuddyPress child theme that displays all of the sortable data above, plus a download link for the mp3, plus a built-in audio player. I am using Custom Field Template for the mp3/wav/aac audio file upload meta box.
Nothing is set in stone right now, as I think I would like to think this through a bit more. That said, I have a great start!
What do you think? Any ideas for improvement?
More posts from themightymo.com
My WordPress Maintenance Process
A few quick things: My WordPress Maintenance Process Demo, Part 1 Transcript: You’ll see immediately after logging in, you see the 11 updates needed as well as some messages. I’m just gonna quickly read. It looks like this. I don’t need to worry about. Are you enjoying Monster Insights? Not really <laugh>. What’s to enjoy…
How to style FacetWP checkbox hierarchy results using jQuery
How to fix SpinupWP ballooning disk space issue
A site we host on Digital Ocean recently went down. It took me a lot of troubleshooting and digging before realizing that the issue was that our disk space was maxed out on Digital Ocean. The site in question needs ~20gb of space, so our 50gb server should be plenty. But alas, there it was…