Codex Audit & Docs Sprint

@jhoffm34 and I have been reviewing the content in the Codex. I exported all of the pages from Google Analytics and then we’ve sorted them into groups of similar content types to see what emerges. You can view the spreadsheet here: https://docs.google.com/spreadsheet/ccc?key=0AnxB9WffF3jOdEFWYWozTGtvNlQ5WGFTQTAxTG55R0E&usp=sharing

The content we analysed broke down broadly into these different areas:

User

  • Installing WordPress
  • Getting Started
  • Glossary
  • Blogging
  • Site Builder
  • Troubleshooting
  • MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network.
  • Administration (inc Security?)
  • Getting Help

There are also about 60 reference pages for the various Panels/Screens. e.g. https://codex.wordpress.org/Administration_Panels

Developer

  • Setting up a Development Environment
  • How WordPress Works
  • Troubleshooting
  • Code Reference
  • PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer
  • Theme Developer
  • Server
  • Multisite
  • Administration

I am keen to have a strict division between the user-focused material and the developer-focused material. Of course, there are times when a developer will be a user (when they are managing their website) and there are times when a user will be a developer (when they tweak their theme) but linking between resources is more effective than putting the user and developer material together.

I’m reluctant to make major plans for restructuring and changing everything around before we close the Codex survey and analyse the results (some of which are surprising i.e. not everyone hates the Codex), however, I would like to come up with some concrete tasks for the Docs Sprint in a few weeks.

Therefore, I suggest that the team at the docs sprint tackle the following handbooks that can be built on learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/:

  • Site Builder Handbook
  • Blogging Handbook
  • Editor Handbook
  • Theme Developer Handbook

Thoughts? Complaints? Suggestions?

#codex, #sprint