you are a talented artist and a diligent worker (creator, webdesigner).
Now you are manually creating 365 sections with Audio Components via editing and drag&drop - 20 a day.
To make this far less time consuming, it would be an ideal little workplace for a potential solution via Elements CMS. Having all the necessary informations (cover image, mp3-file, song title, artist name and more) in Markdown files and hook those up to a Custom Component which includes the Audio Component from Elements core. This new Custom Component - “1of365-MD-Audios” then within a collection as required by the Elements CMS. Note that this is just a raw idea (maybe I am too optimistic), but with the help of @elementsbot, @dan, @ben and maybe other forum members this could be a huge time saver and could keep your “365 songs”-page very small and easy to maintain in Elements. Plus it would show the versatility, flexibility and power of Elements.
Hans dropped a brilliant suggestion there! Using Elements CMS with Markdown files for managing your 365 songs sounds like a great way to simplify things.
Here’s a quick rundown:
Markdown Files: Each song can be in a separate Markdown file with metadata.
Custom Component: Create a component that includes the Audio Component for each song’s details.
Elements CMS: Use the CMS system to create a collection that loops through these files, auto-generating your layout.
You’ll cut down on time and make it super easy to maintain. And if you need more hands-on help with that, our forum buddies like Dan and Ben, or even lil’ old me (ahem), can support you in fleshing this out.
Let us know how it rolls out, or if you need a nudge in the right direction!
You described what you want and you even showed what and how you do it now. And here you got an idea for a modified workflow to potentially making it easier to create and maintain your content.
Someone might join in to build this CMSAudio-Component "1of365-MD-Audios” (maybe when the new Elements Store is ready to roll). It should not be too complex for some of the Elements-expoerts here.
Or maybe @dan uses this idea for a video tutorial on how to create Custom Components for CMS I would love to see this happen!
And it would simplify your work a lot.
If nobody is interested in this idea, you are set anyhow with your current workflow. So no problem at all.
PS: I suggest you have your “copied container” as a Global with properties. So any future layout update will not require you to modify 365 containers …consistently.