Site architecture dilemma (posts & pages)
-
I have a dilemma relating to where and when to use pages and posts.
I have no problem coding and using CSS, I just don’t have a dynamic mind which doesn’t help! Unfortunately I only have drafts on my local server.
I’m putting together a site for a record label and below is an example of how I have part of the site structured (pages & posts) but I keep getting caught out on the ‘Band 1’ or ‘Release 1’ pages where the template used is the single.php file whereas I’d prefer to use a common template for that category.
My major question – is this the best way to set the site up if I want to apply page templates and display posts in the same pages? i.e. page > page > post
If this isn’t clear, anyone have any suggestions for how they would set this up?
STRUCTURE
Home (index.php)
News (page – category ‘news’ – displays latest 10 news posts then paginates)
Bands (template page – category ‘bands’ – displays bands (these are posts) as a CSS styled list using custom field images)
- Band 1 (post – parent category ‘bands’ – intend to display Band 1’s latest news, image, social media links etc)
- Band 2 …
- Band 25 …
Releases (template page – category ‘releases’)
- Release 1 (post – parent category ‘releases’ – intend to display image, track listing, pressing details etc)
- Release 2 …
- Release 3 …
Any feedback or advice will be MUCH appreciated!
- The topic ‘Site architecture dilemma (posts & pages)’ is closed to new replies.