[wp-trac] [WordPress Trac] #14746: Post Formats

[WordPress Trac]

#14746: Post Formats
----------------------------+-----------------------------------------------
 Reporter:  ryan            |       Owner:                             
     Type:  task (blessed)  |      Status:  new                        
 Priority:  normal          |   Milestone:  3.1                        
Component:  Template        |     Version:                             
 Severity:  normal          |    Keywords:  ongoing-project ui-feedback
----------------------------+-----------------------------------------------

Comment(by SmallPotato):

 Replying to [comment:118 mikeschinkel]:
 > Replying to [comment:116 SmallPotato]:
 > > the problem with soliciting opinions for a set of standard formats is
 it's more time consuming. individuals and groups have their own list of
 must-have or standard formats. asides, galleries, quotes, events, links,
 images, videos, and audios to list a few. even with a large enough pool of
 voters, not all popular formats would be included if there's a limit on
 number of formats you can include.
 > >
 > > maximum portability means standardizing with a minimalistic set of
 features per format. for a format like Aside, that could work. for more
 complicated formats, it's easier said than done. time is needed to figure
 out what's necessary/unnecessary for each popular format. leaving it in
 the hands of users and developers will speed up this process, which is why
 setting standards from the top down and making people wait will be more
 time consuming.
 > >
 > > flexibility and portability may be equally important, but if you leave
 room for flexibility to grow first, it will sort out the standards for
 portability quickly and precisely.
 >
 > Also, there's also a benefit in ''embracing constraints''.  There have
 been several people promoting the idea of embracing constraints lately,
 [http://www.onextrapixel.com/2010/08/30/embrace-constraints-how-limiting-
 yourself-wont-limit-your-designs/ for example]. This probably started
 recently [http://gettingreal.37signals.com/ch03_Embrace_Constraints.php
 with 37 Signals ''"Getting Real"'' book] (although I'm really not a fan of
 37 Signals I do generally agree with them on this topic.)
 >
 > Some of my best work has come from when I've embraced constraints given
 to me, and some of my worst has been when I allowed myself uncontrolled
 freedom to implement whatever.

 i see your point. however, it seems neither of the two examples referenced
 are applicable. (correct me if i'm wrong. i might be confused.)

 designers use constraints for direction in order to finish the job quickly
 and objectively. it's unlike limiting post formats.

 in design, the client tells the designer you can use anything you want to
 design the site, but work around my needs. admittedly, that is setting
 standards from the top down in which constraints are helpful. in limiting
 post formats, you're the designer telling the client only Photoshop tools
 are available, no Illustrator, therefore, no illustration or vector work.
 that's setting standards from the top down for your convenience, not for
 the good of the clients or theme users.

 second example referenced an experiment, which i will not summarize here.
 in that experiment, the controller knew what to do and the audience
 didn't, which means more tools = higher learning curve for the audience to
 get right. in WordPress, the audience or theme users actually know what
 they want. they're the ones who should determine what needs to be built.
 from their demands, we filter out the necessary constraints for each
 format.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14746#comment:121>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software