WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #21951, comment 24


Ignore:
Timestamp:
09/24/12 18:52:21 (2 years ago)
Author:
iandstewart
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21951, comment 24

    initial v1  
    22> But when you look at it, wouldn't it be cleaner if Twenty Twelve had a date.php, category.php, and tag.php? I'm thinking about the approach a user would take, trying to customize their theme, probably from the theme editor, without knowing a thing about WordPress. (Been there, many years ago.) I'd rather leverage the existing hierarchy than fill up a catchall template with conditionals. 
    33 
    4 I used to feel the same way, and somewhat strongly, until I realized that in practice this seems to rarely happen with themes and that what you have is a bunch of templates hanging around that are modular for no particular reason. I think, in the end, it's actually easier to grok archive templates with those conditionals for the title-ey bits. Anyone needing to change anything more, developer-ey people, will know they can take advantage of the template hierarchy in a fork or a child theme. It's more code in the one template but more templates feels way lighter. Anecdotally I've seen lots of themers saying the same thing in forums. 
     4I used to feel the same way, and somewhat strongly, until I realized that in practice this seems to rarely happen with themes and that what you have is a bunch of templates hanging around that are modular for no particular reason. I think, in the end, it's actually easier to grok archive templates with those conditionals for the title-ey bits. Anyone needing to change anything more, developer-ey people, will know they can take advantage of the template hierarchy in a fork or a child theme. It's more code in the one template but more templates feels way heavier. Anecdotally I've seen lots of themers saying the same thing in forums.