"Format: Default" provides no info, and default might change

[lloydbudd]

"Format: Default" provides little info, and a site might want to change which is the default.

Some discussion: ​http://wpdevel.wordpress.com/2010/11/05/post-formats-in-core/#comment-12462

Possible solutions

"Format: Blog Post"

"Format: Article"

ENV

WP trunk r16590 (3.1-beta1-16590)

Additional Details

Post Formats are a blesed task, #14746.

"Default" also has some of the same characters as "Draft".

[nacin]

It's not supposed to be a default that changes.

I'd almost rather go with "Format: None" if anything.

[lloydbudd]

Replying to nacin:

It's not supposed to be a default that changes.

Not the Default that changes, but the default selected that changes. ie. on a status site, I'd always want the default selected to be Aside.

I'd almost rather go with "Format: None" if anything.

I'm not sure that is better because that begs everyone to look at what else is in the drop down, and again each time they forget what Default or None means.

[markmcwilliams]

Replying to lloydbudd:

Not the Default that changes, but the default selected that changes. ie. on a status site, I'd always want the default selected to be Aside.

On a related sidenote, can you actually specify a 'default' to be used?

[westi]

Format: None is probably better here as that is what we mean.

[lloydbudd]

Replying to westi:

Format: None is probably better here as that is what we mean.

Is it what we mean? The formatting is defined by the theme's templates, just like before when there were no other options.

Besides, users won't get what we mean, and it would becomes confusing on a theme that is coded around another template.

The format is "Blog post".

[lloydbudd]

Replying to westi:

Format: None is probably better here as that is what we mean.

If we are going to display something it should be rich info, not the safest path.

[lloydbudd]

Replying to markmcwilliams:

On a related sidenote, can you actually specify a 'default' to be used?

If that can't be defined in the theme, then it should be trac'd and that enhancement added.

[lloydbudd]

Replying to lloydbudd:

Replying to markmcwilliams:

On a related sidenote, can you actually specify a 'default' to be used?

If that can't be defined in the theme, then it should be trac'd and that enhancement added.

Actually, maybe that helps reveal a more optimal solution.

"Format: Blog Post" is the name of "none" unless programmatically set up in the theme to use a default selected of "Format: Themed" ("none" behind the scenes), in which case they could also explicitly create a "Format: Blog Post" if a relevant alternate relevant for the site.

[lloydbudd]

Replying to lloydbudd:

"Format: Blog Post" is the name of "none" unless programmatically set up in the theme to use a default selected of "Format: Themed" ("none" behind the scenes), in which case they could also explicitly create a "Format: Blog Post" if a relevant alternate relevant for the site.

To put it more clearly, and correct my previous thought.

A theme can change the default selected format to be any one of the standard types, and if not one of the standards then this would be the only non-standard formatting, "Format: Themed". "None" will still be "Format: Blog Post" which a theme can include in the list or hide like the other standard formats.

I think that something like that would be a good balance.

[nacin]

Non-standard post formats are not supported.

I don't see a strong use case for there to be a way to set a particular post format as the new default selection. That can be handled if a theme wishes to provide its own UI. It could be also handled when the auto-draft is triggered, so it's rather trivial to do in a plugin.

"Format: blog post" is wrong. These are all blog posts. We're just evaluating the different type of post. "Format: none" or "Format: default."

[lloydbudd]

There must be a Design Commandment that reads, "Thou shall not put none or default in the UI."

[Otto42]

Tumblr uses "Text" as their default. Kinda fits.

[JohnONolan]

I agree with Otto - "none" is definitely the most confusing option, can't expect users to understand that. "Text" makes sense seeing as post formats are all about content types - and the default content type is indeed text.

[michaelh]

Can it be more than one word?

Examples:

• Not assigned

• No designation

• Empty

• No format specified

[JohnONolan]

Those are all just the same as "none" - they don't have any greater or lesser meaning.

[GamajoTech]

Replying to Otto42:

Tumblr uses "Text" as their default. Kinda fits.

Except Aside and Status are also a textual content type.

How about Format: General / General Post?

[jane]

Basic or Basic Post would be my choice. Also need to move out of pub box and into a meta box with radio buttons.

[ryan]

Whatever is picked should never, ever make it to the DB. We don't want to clutter the DB with something that is totally unnecessary and meaningless. The absence of a format in the DB means "Default, None, Basic" whatever.

[markjaquith]

The core team conferred and we considered about a dozen alternatives. We settled on "Standard." It implies that it is the familiar option that people have been used to before 3.0, but it doesn't imply "defaultness." That is, you could default to "Aside" and it would make sense to offer "Standard" as an option.

This has the potential to turn into a bikeshed. Resist! :-)

[markjaquith]

In [16679] The name of the standard post format is now "Standard" (might offer ability to change default). fixes #15582

[markjaquith]

(In [16682]) Missed a s/default/standard/ in [16679]. props PeteMall. see #15582.

[markjaquith]

(In [16683]) Argh. Missed another s/default/standard/ in [16679]. Any others? see #15582.

[markjaquith]

(In [16693]) Another s/default/standard/. see #15582