search

justintadlock / content-type-standards

WordPress community-curated standards for common post types, taxonomies, and metadata.
302 stars 26 forks source link

Isn't a portfolio post type a bit too generic? #18

Closed daprela closed 10 years ago

daprela commented 10 years ago

Hi everyone, at a first sight, it makes sense having a portfolio post type but when you look closer at it there are many issues. There are dozens of professionals that could publish a portfolio, how can you standardise taxonomies and custom fields (provided that they will also added) for all of them? For example, an architect will need totally different taxonomies than a photographer, or a comics artist. How is it possible to do something that is general here?

justintadlock commented 10 years ago

We need to look at the 80% rule here that WordPress follows. Design the system for the majority of users. If you look at the vast majority of portfolio plugins and what most users are doing with them, there are certain patterns that we can use to make some decisions with.

Let's say you come along and want to build a portfolio plugin that's specifically geared toward comic artists. You already have a working base. However, there might be niche-specific stuff you need to add. You can either build your own plugin to handle this entirely. Or, you can build an add-on plugin for one for the plugins that follow the standard.

Also, if you feel like something is an important enough use case to get its own standard, it can be done within this project.

justintadlock commented 10 years ago

I'm going to close this one as it doesn't have any traction at this point.