I’ve done something similar, albeit for a music podcast where each podcast featured certain bands and albums, and each band was listed with their albums and what podcasts they were featured in.
One way to do that is through EE relationships, that is a lot of use of the Relationships field type.
First off set up channels for Tracks (songs), Albums, Playlist and Gallery. You’ll want to set up custom field groups for each Channel, something like this:
Bands
Albums
Tracks
Playlist
I’ll leave out the gallery for the time being as there are numerous ways to approach it.
So for example
you can call, say and album entry, using the Relationship field you can then pull in the band info and tracks for that album on the same page
you call can a band entry then you can pull in related albums and tracks
you call an album entry then you can pull in related tracks and band info.
So what should I name a category for this? Should I just name it Music?
Let’s say I have 10 albums and 5 of them are like remix collections or specific genre album like an instrumental lounge albums.
Ex: 10 Albums The first 5 albums are volumes for a specific genre such as chill out/lounge. The 6th to 10th albums are more like game music.
In the backed the category group would be called “Music genre” - that’s just a name that appears on the publish page, so when you publish a band/album/track you know what the categories are for. In another scenario you may have a category group for say, Countries, in which you’d have categories for USA, Canada, UK, France etc
The actual categories in the Music genre group would be say Rock, Hiphop, EDM so when you output your menu it may read something like:
[Title] Genres [Link] Rock [Link] Hiphop [Link] EDM
Good stuff!
Statuses, yes you could use them to add another level of classification over and above categories. What I normally do is add a Custom status group for each channel and maybe add a “Featured” status to each. That would enable you to “feature” any band, album, track etc.
A good use for using statuses may be to feature a number of albums but only show one at a time at random, the al;bum shown would be picked from all those that have a status of Featured.
Good stuff! Statuses, yes you could use them to add another level of classification over and above categories. What I normally do is add a Custom status group for each channel and maybe add a “Featured” status to each. That would enable you to “feature” any band, album, track etc. A good use for using statuses may be to feature a number of albums but only show one at a time at random, the al;bum shown would be picked from all those that have a status of Featured.
Okay, cant find a tag for Status on ee so means cant output only the ‘feature’ status of that ‘album’ channel. So how do u code that for the frontend as an example?
Because im thinking of creating more than 3 statuses to experiment for use on my youtube and blog site like for frontend classification purpose:
Featured(displayed after masthead row) Awarded(displayed on left sidebar), Recommended(displayed on footer 7 links per column, 5 columns, 2 rows)
Backend classification purpose: Draft - preliminary(rough sketch) Draft - secondary(if entry is ready to categorize, assign a page or template) Draft - Final(if entry is ready to finalize or submit) Completed(If entry is ready to choose either Open, Featured, Awarded, Recommended)
You can create status “groups” where each group can have as many custom statuses as you need, then assign each status group to a channel, see Admin > Channel admin > Statuses for EE2, or Developer > Channel manager > Status groups for EE3.
To limit output to a specific status for any channel you add a parameter, eg:
{exp:channel:entries channel="mychannel" status="Featured"}
{title}
{/exp:channel:entries}Or if you wanted to display entries from more than one status:
{exp:channel:entries channel="mychannel" status="Awaarded|Featured"}
{title}
{/exp:channel:entries}Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.