[wp-trac] [WordPress Trac] #9215: Add versionsing to Codex
WordPress Trac
wp-trac at lists.automattic.com
Mon Feb 23 13:13:04 GMT 2009
#9215: Add versionsing to Codex
-----------------------------+----------------------------------------------
Reporter: sampablokuper | Owner: matt
Type: feature request | Status: new
Priority: normal | Milestone: 2.8
Component: WordPress.org | Version:
Severity: normal | Keywords:
-----------------------------+----------------------------------------------
Several good open source web-frameworks/CMSs, e.g.
[http://www.djangoproject.com/documentation/0.96/overview/ Django], apply
versioning to their user manuals (notice the "0.96" in the preceding URL)
to match their releases. WordPress doesn't, which leads to problems like
[http://codex.wordpress.org/index.php?title=Talk:Creating_a_Static_Front_Page&oldid=55994#What_do_we_want_from_this_page.3F
this].
I suggest WordPress adopts this kind of versioning for its user manual,
the [http://codex.wordpress.org Codex]. The sooner, the better, IMHO.
The process would involve copying the existing documentation to a new
version number for each significant release, and then modifying only the
pages of the new Codex copy that referenced parts of WordPress that had
changed in that release.
If this was done, it would be a big boon for people developing sites with
WordPress and people who want to work on the documentation but who aren't
sure which version(s) to target.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/9215>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list