[wp-trac] [WordPress Trac] #26879: Hello, new users. Here is an Error.
WordPress Trac
noreply at wordpress.org
Thu Mar 6 07:11:16 UTC 2014
#26879: Hello, new users. Here is an Error.
-------------------------------------------------+-------------------------
Reporter: mrtortai | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 3.9
Component: Upgrade/Install | Version: 3.0
Severity: normal | Resolution:
Keywords: has-patch 2nd-opinion docs-feedback | Focuses:
needs-testing |
-------------------------------------------------+-------------------------
Comment (by mrtortai):
Hello Hanni,
Thank you for the great content feedback.
> "We'd love you to join the family."
Yes agreed. A couple possible alternatives:
a) The description does not include any mention of WordPress being free or
Open Source which is an essential part of WordPress. It would be a good
idea to include a short paragraph here.
b) Just a smiley face here could be fun and welcoming: :-)
> “core software”.
Very much agreed. That should be removed.
> OK, I admit it, this is a ridiculous nitpick, but I’m bothered by the
use of website and then merely two lines later (one sentence), “site”.
Good catch. Very much agreed as well!
> how about replacing “thousands” in “there are thousands of plugins and
themes” with “countless”?
"Countless" could mean many dozen and doesn't sound nearly as impressive
as "thousands" in my opinion.
> " To get started, we need some information on the database" - what about
“about” in place of “on”. This doesn’t read well to me. I actually would
+1 for Siobhan’s overhaul of the sentence to “Before getting started, you
need to configure WordPress.”
The sentence, “Before getting started, you need to configure WordPress.”
isn't very informative and "configuring WordPress" sounds hard. I like how
the current sentence is very casual and makes the process sound easy. ("To
get started, we need some information on the database").
> “Table prefix (if you want to run more than one WordPress in a single
database)” WordPress instance? The whole parenthesis is potentially
redundant. Even more so when I go on to the next step and see the
explanation there…. So, yes, this can explanation doesn’t need to be in
two places.
Yes I would also vote to remove the parenthesis here.
> Is the wp-config explanation actually needed? What about displaying it
only if something goes wrong?
I do like the wp-config explanation here because personally I'd like to
know what the installer does. Without the patch, there is a dark bold
paragraph here warning about what to do if it the install, "doesn’t work".
So the new version aims to be more friendly without hiding the explanation
of what the installer does.
> “Need more help? We got it.”
I actually quite like that :-)
> “Oops, the Table Prefix field should not be empty. “ Correct, it
“shouldn’t” in terms of being good practice. But, also, in this case it
“cannot” be empty. So, perhaps can't could be used instead here.
Good point!
> I'll go ahead and create the patches for the instances in which @siobhan
and I are in agreement later on today.
Sounds great! Thanks for the help!
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26879#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list