Isaac Keyet 12:38 pm on December 28, 2012
Tags: handbook ( 23 )

Got a table of contents ready for the…

Got a table of contents ready for the Mobile Handbook – and spent the last few hours thinking about how to best greet new users. Added/rearranged articles and categories as I saw fit but let’s discuss all of this.

For reference: https://make.wordpress.org/mobile/handbook/

Also started writing the Design Contribution basics.

So, thoughts on the ToC? We also need people to write some of the new pages.

#handbook

Dan 3:42 pm on December 28, 2012

How about we group the information under each app? Each one would have tools and requirements, tutorials and guides, best practices, references and testing instructions. Otherwise you would have to jump around to find all of the information for one app.
- Isaac Keyet 4:29 pm on December 30, 2012
  
  I like that, but there are also some overarching topics – design, testing, support could all be written independently from the apps.
  
  Rachel, @raggedrobins: we’ll make these changes for now since they’re only structural. We can switch it around if need be.
rachel_mccollin 12:25 pm on January 9, 2013

Could the information perhaps be arranged in a modular way, so that the ToC links to overarching topics and to individual apps? Then if a user clicked on the topic, they would see an overview plus the relevant content for each app, and if they clicked on an app they would see an overview (and anything app-specific) plus the relevant topic content for each app. I guess it would mean using tags – I haven’t worked on Docs before so don’t know how straightforward it would be. Shoot me if I’m making things too complicated! 🙂
- Isaac Keyet 3:39 am on January 10, 2013
  
  The theory is that most potential contributors would only be interested in one platform – and since all code bases are different there are different ways you would go about most things (set up, guides, best practices, references, testing). Some over-arching things may make sense to have outside the per-app structure (e.g. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., Design guidelines). That’s my opinion at least. Feel free to elaborate, maybe I misunderstood you!