Changes between Initial Version and Version 1 of Ticket #41362, comment 5
- Timestamp:
- 08/10/2017 05:15:30 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #41362, comment 5
initial v1 1 1 @dingo_bastard I second @kylejennings83 suggestions and hope you'll consider his patch. I totally understand your recommendation about handling CPTs in a plugin. My experience with clients is actually the opposite though — they want everything in one clean place (the theme directory) that represents the architecture and style for the site. In a plugins directory, there's often confusion about what "should" be activated (especially after an over-excited intern goes through and installs a hundred plugins). Regardless, we can all argue convincingly why you'd be (crazy/correct) to put things like that in a (plugin/theme) depending on the situation. 2 2 3 Something I've always loved about WordPress is there's no right way to "use"it — yes people have built blogs, but they've also built movie rating sites, cooking sites, (I think even the first versions of OpenTable were built on a hacked-together WP install?) That's why 25% of the internet is powered by it.3 Something I've always loved about WordPress is there's no "right way" to use it — yes people have built blogs, but they've also built movie rating sites, cooking sites, (I think even the first versions of OpenTable were built on a hacked-together WP install?) That's why 25% of the internet is powered by it. 4 4 5 5 I wish this same openness applied to architecture. While WP wasn't designed to be MVC in 2003; it *is* an MVC app. How do I know? Tens of thousands of devs use it as an MVC app every day! (through Timber and others like it). I hope the Core team will consider this (and patches) like that to make it more conducive to MVC-style development