Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#10996 closed enhancement (worksforme)

Replace 'Blog' with 'Site' in admin

Reported by: scribu Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords: has-patch
Focuses: Cc:


WordPress is about web publishing, right?

So why limit it to "blogging software" by using 'blog' everywhere?

Attachments (1)

blog_site.diff (24.9 KB) - added by scribu 9 years ago.
Replace 'blog' with 'site' in the admin area

Download all attachments as: .zip

Change History (11)

9 years ago

Replace 'blog' with 'site' in the admin area

#1 @filosofo
9 years ago

WordPress MU uses "site" to distinguish something as referring to that domain at large as opposed to its individual "blogs." So to avoid confusion you might need to come up with another term with which to replace "blog."

#2 @Otto42
9 years ago

  • Milestone changed from 2.9 to Future Release

-1. I don't see the point in breaking all the translations over something this trivial.

Combine it with other complete rewordings of, well, everything in the entire interface, and I might change my opinion. Especially if combined with inline docs.

A decent rewriting and/or adding of inline documentation project might be in order.

#3 @strider72
9 years ago

Otto -- I'm confused. Are you saying we need to reword the entire interface?

Fix where you need a fix, but why fix where you *don't* need a fix? (Or am I misunderstanding you?)

Not breaking translations is a legitimate point. I'm just not getting your second statement.

filosofo -- Good point since WordPress doesn't necessarily control an entire site (i.e. subdirectory installs). But what the heck else could you call it? Perhaps MU should use "domains" and WordPress can use "site"... or something?

#4 @Otto42
9 years ago

strider72: What I'm saying is that I don't think it's worth breaking translations for this minor of a change. If we're going to break translations, break them for a better reason. Such as, for example, to add context-sensitive help or inline documentation or half a dozen other possible reasons.

In other words, put this off until it can be merged into a bigger change, like one that's going to change a lot of the wording anyway.

#5 @strider72
9 years ago

Otto --

Okay. Agreed. Not on its own worth breaking translations over. :)

Something to think about for down the road -- whenever this does happen...

WordPress *is* primarily a blog platform, and that is the way it is billed. Instead of changing the word "blog" to something else, perhaps we could simply add in a hook to allow a theme or plugin to change the word throughout. Thus WordPress remains primarily blog software, but if used for something else can easily be altered.

Some things can simply be changed -- "Blog URL" etc. should probably just be changed to "Site URL" or something else more generic; but in other places (posts etc.) a hook to change "Blog" to, say, "News" or whatever might be a good idea.

#6 @otto42
9 years ago

You should be able to do it now, with the hooks in the translation system. Probably a simple preg_replace to find and change it everywhere, if you can think of the correct terminology to use. :)

#7 follow-up: @azaozz
9 years ago

Otto42 is right, with a custom .mo file you can change absolutely all strings in WordPress, replace posts with Que-cards or Information Bulletins and comments with Messages From Beyond if that's needed. And it takes very little maintenance, usually just a rebuild on each major version.

#8 in reply to: ↑ 7 @Otto42
9 years ago

Replying to azaozz:

Otto42 is right, with a custom .mo file you can change absolutely all strings in WordPress,

Or use the gettext filter. No need to make a custom translation for just one word replacement.

#9 @scribu
9 years ago

  • Resolution set to worksforme
  • Status changed from new to closed

#10 @scribu
9 years ago

  • Milestone Future Release deleted
Note: See TracTickets for help on using tickets.