[wp-trac] [WordPress Trac] #10835: Readme.html cleanups, rework

WordPress Trac wp-trac at lists.automattic.com
Wed Sep 23 21:17:07 UTC 2009


#10835: Readme.html cleanups, rework
-----------------------------+----------------------------------------------
 Reporter:  niallkennedy     |       Owner:            
     Type:  enhancement      |      Status:  new       
 Priority:  normal           |   Milestone:  Unassigned
Component:  Upgrade/Install  |     Version:  2.9       
 Severity:  normal           |    Keywords:  has-patch 
-----------------------------+----------------------------------------------
 I reworked readme.html and related CSS in an attempt to better explain
 WordPress to first-time users.

 == Bigger changes ==

  * Break up "recommendations" section into "requirements" and
 "recommendations" sections. Matches wording in
 [http://wordpress.org/about/requirements/ WP.org requirements page].
  * Link to PHP and MySQL homepages (and cron on Wikipedia), just in case
 it's not obvious to someone.
  * Add mod_rewrite as a recommendation.
  * Note that WordPress 1.5 template changes only are likely to apply if
 you have a WordPress install from before Feb 2005.
  * Link WordPress logo on top of page to WordPress.org. Add image
 dimensions to avoid page redraw.
  * Change links and text for XML-RPC tools to reflect their current names
 and homepages. This paragraph seems geared towards the blogging world of
 2005; there have been a few name and ownership changes since.
  * Add a link to WordPress import tools list in wp-admin.

 == Smaller changes ==

  * New css for dt and dd elements to match li and p font size and spacing.
  * Add title attributes to some links to better describe destination
 content (user-facing in tooltip).
  * Convert named HTML entities to UTF code point equivalents to match
 document style, doctype syntax, and lookup speed.
  * Add nofollow link relationship to install and upgrade links to prevent
 discourage search crawlers hitting those links.
  * Add abbreviations (abbr) where appropriate to expand content meaning.
 e.g. <abbr title="WordPress">WP</abbr>
  * Remove suggestion to bookmark and constantly check wp dev blog.
 Encourage users to check their admin dashboard module instead.
  * Explicitly specify GPLv2 instead of just GPL.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10835>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list