[wp-meta] [Making WordPress.org] #240: Create an IA for devhub

[Making WordPress.org]

#240: Create an IA for devhub
--------------------------+-------------------------------------
  Reporter:  siobhan      |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  high         |  Component:  developer.wordpress.org
Resolution:               |   Keywords:
--------------------------+-------------------------------------

Comment (by siobhan):

 Thus far:

 developer.wordpress.org
 developer.wordpress.org/reference/
 developer.wordpress.org/reference/?s=
 developer.wordpress.org/reference/functions/
 developer.wordpress.org/reference/functions/some_function
 developer.wordpress.org/reference/hooks/
 developer.wordpress.org/reference/hook/some_hook
 developer.wordpress.org/reference/classes/
 developer.wordpress.org/reference/class/some_class
 developer.wordpress.org/reference/class/some_class/some_method
 developer.wordpress.org/reference/source_files/
 developer.wordpress.org/reference/source_files/file-name
 developer.wordpress.org/reference/versions/
 developer.wordpress.org/reference/versions/version-number
 developer.wordpress.org/resources/
 developer.wordpress.org/resources/some_resource (e.g. dashicons)
 developer.wordpress.org/blog/

 Here's where I'm not sure yet what the structure should be. Here are a
 couple of options:

 developer.wordpress.org/themes/
 developer.wordpress.org/themes/handbook
 developer.wordpress.org/themes/handbook/some_handbook_page
 developer.wordpress.org/plugins/
 developer.wordpress.org/plugins/handbook
 developer.wordpress.org/plugins/handbook/some_handbook_page

 Pros: leaves space for the section on themes and plugins to grow beyond
 the handbooks
 Cons: we need to create a separate landing page for themes/plugins. If we
 don't have any resources beyond the handbooks (and none are planned), the
 /themes/ and /plugins/ will be redundant

 OR

 developer.wordpress.org/handbooks/
 developer.wordpress.org/handbooks/theme-developer/
 developer.wordpress.org/handbooks/plugin-developer/
 developer.wordpress.org/handbooks/some-other-handbook/

 Pros: keeps the type of documentation together so a person can go and find
 them in one place
 Cons: grouping documentation together by theme and plugin makes it clearer
 where the developer needs to go

 OR

 developer.wordpress.org/theme-developer-handbook/
 developer.wordpress.org/plugin-developer-handbook/

 Pros: simpler structure. We won't need to create additional landing pages
 Cons: no scope to grow beyond the handbooks

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/240#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org