[wp-trac] [WordPress Trac] #26879: Hello, new users. Here is an Error.

[WordPress Trac]

#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 Hanni):

 This has to be right up there for the best first bug report and subsequent
 patch(es), @mrtortai! Wow! :)

 Please forgive my incoming wall of text, I have a great deal of thoughts
 about your wonderful ideas.

 Some notes on the aforementioned thoughts as the text stands right now in
 26879-8.patch:


 {{{
 wp-load.php
 }}}


 1. My first thought,underlined even further after seeing @siobhan's
 comment to that effect refers to the last line of the wp-load.php text.

 "We'd love for you to join a family", whilst perhaps appropriate (?) for
 the about page, feels too "in your face" for a user’s very first
 interaction with the software. It's a little too over-eager, over-
 friendly. I liken it to that rather uncomfortable feeling in a
 conversation with a new acquaintance who, whilst absolutely lovely, and
 well intentioned, is clearly trying too hard and thus making the situation
 needlessly awkward.

 2. Ditto with regards to “core software”. That’s jargon to an outsider,
 without a shadow of a doubt. How about just this software, or this
 project? Project may not be ideal, as it’s  introducing yet another word /
 community specific thingamajig. I apologise for not having an alternative
 idea here.


 3. 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”.
 This is an unnecessary inconsistency, IMHO.

 4. In the same vein as @nacin’s suggestion to remove the version number
 above, how about replacing “thousands” in “there are thousands of plugins
 and themes” with “countless”? It’ll stand the test of time better, and (to
 me at least) is a friendlier word. This may be a British, or just “Hanni”
 point of view, though.


 5. Button text could be shorter. Title case looks odd in this case with
 “Let’s Get Started!” What about “Let’s Go!” or “Let’s go!”. I realise this
 doesn’t have quite the same connotations so.. will mull this over a bit
 more. (OK, this is hilarious, I wrote this before clicking on the button,
 and now see that the next screen uses “Let’s Go!” in a far more
 appropriate context. This perhaps makes the above point moot). How about
 "Get Started?" It's less friendly, though.



 {{{
 setup-config.php
 }}}



 1. 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.”

 2. “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.

 3. Is the wp-config explanation actually needed? What about displaying it
 only if something goes wrong? If it is needed then an alternative to "good
 stuff' could perhaps be found. I'm sorry that I'm struggling to think of
 one right now.

 4. “Need more help? We got it.” is another slightly strange sentence. Why
 not something like “You can find help here.” “If you need help, ..” or
 something...

 5. “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.

 I'll go ahead and create the patches for the instances in which @siobhan
 and I are in agreement later on today. I'm happy to do more, if anyone
 else thinks any of the above proposals make sense.

 This is fantastic, @mrtortai!

--
Ticket URL: <https://core.trac.wordpress.org/ticket/26879#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform