[wp-trac] [WordPress Trac] #47267: Let's improve the writing -- and the message -- in the WordPress sample post.
WordPress Trac
noreply at wordpress.org
Tue May 14 18:04:02 UTC 2019
#47267: Let's improve the writing -- and the message -- in the WordPress sample
post.
--------------------------+-----------------------------
Reporter: marybaum | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Text Changes | Version: trunk
Severity: normal | Keywords: needs-patch
Focuses: |
--------------------------+-----------------------------
Here's the current copy in the WP sample post:
"This is an example of a WordPress post, you could edit this to put
information about yourself or your site so readers know where you are
coming from. You can create as many posts as you like in order to share
with your readers what is on your mind."
For starters, let's fix the opening sentence to make it correct English:
"This is an example of a WordPress post. You could edit this to put
information about yourself or your site so readers know where you are
coming from.
... "
But we can also be a little more helpful. If someone needs to know what a
post is, or what a page is, maybe they'd appreciate something more like
this:
"This is an example of a WordPress post. Think of a post as an article in
your own magazine, and write from your own perspective. Create as many
posts as you like, or as it takes to make your case. "
Here's a dummy post I use with a client who might be a little more
sophisticated:
`
{{{
<p>This is a sample intro paragraph we can use to hook visitors into
reading the article. With Gutenberg – I mean the block editor – and some
shrewd changes on the style sheet, we can make this blend in or stand
out.</p>
<p>
Up to now we’ve shown this dummy copy to be a whole lot longer than it’s
likely ever going to be, even if we have a long story to tell, because
we’ll want to break up that longer story into a series of posts.
</p>
<h3>
Taking the measure.
</h3>
<p>
Another thing we do for readability is to spec a maximum character width
on the paragraph tag. There’s even a unit for that! It’s the ch. I set the
<p> element to a maximum width of 55 to 75 characters.
</p>
<p>
In traditional typography, the line length is called the measure. If you
want to impress someone (from a very short list!) in a meeting, you can
say, "I think a 75-character measure is fine, but 55 characters is a lot
more comfortable for some people." You'll sound like you've been setting
type for 40 years.
</p>
<h3>
This is a sample subhead.
</h3>
<p>
I tend to use subheads that stand out at smallish sizes: they’re bold, or
script, or they might be highly decorative. Their purpose is to keep your
reader interested in discovering the next little bit of copy--or to tell
the next part of the story in a nutshell, or both. Designwise, if there’s
a distinctive typeface in your logo, you’ll likely see it repeated in
subheads, where they’ll help the content pull the reader’s eyes down
farther into the copy.
</p>
<p>
That’s the hope, anyway.</p>
}}}
`
So there are lots of ways to fix this, from the sublime to the stupidly
simple. Do we want to consider the easy grammatical fix as has-patch? Do
we want to involve another team, like Marketing? If we add subheads and
explain why they're a good idea, we'll patch the CSS accordingly.
So I guess this is a needs-patch if it gets blessed.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47267>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list