"Recommendations" Should Be "Requirements"

[miqrogroove]

The title <h1>System Recommendations</h1> in readme.html is ambiguous and should be changed.

​http://core.trac.wordpress.org/browser/trunk/readme.html#L57

From Beasts at

​http://wordpress.org/support/topic/342808?replies=2#post-1319345

[nacin]

In that case, a new recommendations section should be set up, with mod_rewrite (which would be new, but is listed elsewhere outside the readme) and a link to WordPress.org being the recommendations.

Or, we strip the 'link to wp.org' recommendation entirely. Point is we need to make sure that isn't under a "Requirements" header cause it isn't.

[ryan]

There's talk of removing readme.html in 3.0 since few people read it and it is oft neglected.

[hakre]

as per ​http://wordpress.org/about/requirements/

I like to have a readme shipping in the package, but I'm okay with a textfile, it must noch be HTML.

[dd32]

but I'm okay with a textfile, it must noch be HTML.

I dont see the harm in shipping a pretty document. WordPress is built upon Typography, so shipping a text document seems lazy.

Everyone who uses WordPress will have a Web Browser handy to view the document in.

[dd32]

Perhaps instead, This should be split into "System Requirements" and "System Recomendations" like most modern software does.

We require PHP 4.3, However, We could recomend PHP5 with the Date extension enabled for example.

I think We should make it clear that some features require later versions of PHP.

[dd32]

Closing this as a duplicate of #10835 (Readme.html cleanups, rework) as it has a much larger overhaul and IMO, makes a better Requirement/Recomendations section.