Here is an updated todo list for the Mobile Handbook. I’ve put names next to some items as a suggestion of who might be a good fit for a topic and in most cases I’ve doubled up our developers since they have big demands on their time. Its not complete so please feel free to grab an item that interested you or take your name off a topic to let someone else have a go.
I’ve also consolidated some items into General Guides to avoid having some single page sections. Some of the pages don’t have stubs and need to be created. The contents list on the handbook front page is a little out of date at this point and we might just remove it and go off what is in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. TOC. Its going away at some point anyway.
iOSiOS The operating system used on iPhones and iPads.
- iOS – blank. Should be the introduction. @koke @sendhil
- Tools & Requirements – incomplete. Needs to talk about pods & other dependencies. @koke @sendhil
- Best Practices – blank. @koke @sendhil
- Tutorials and Guides – blank. @koke @sendhil
- References and Useful Resources – blank. @koke @sendhil
- Testing Instructions – blank. @koke @sendhil
I moved the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Guidelines stub to the Contribute Style section since it seems a better fit there. The “Enabling Safari’s Web Inspector on iOS” topic from Tips and Tricks might be a good fit under Tutorials and Guides.
Other Apps
- Other apps – blank. Should be the introduction. @aerych
- webOS – blank. @beaucollins
- Nokia – blank.
I think it makes sense to devote a short page to each of the other platforms so I’ve added those items. I think the content can be an abbreviated version of what we’re doing for the other platforms. Push back if I’m off in left field here.
Also, we have some great documentation that Sayak wrote for the webOS app that could probably have a home here.
Contribute Design
- Contribute Design – incomplete. Looks close to done but a lot of the links don’t go anywhere. @hugobaeta
- Color Pallet – incomplete. Honestly this could be marked done but it might be nice to have a screen shot or two showing how the colors play in the apps.
- Fonts – blank. @hugobaeta
- General Guidelines – blank. @hugobaeta @isaackeyet
- iOS – blank. @koke @hugobeata @isaackeyet
- Android – blank. @mrroundhill @hugobaeta @isaackeyet
- Windows Phone – blank. @daniloercoli @hugobaeta @isaackeyet
I’m not sure we need to include styles for the legacy BlackBerry app, mostly because there is more demand for native BB10 and we’re not actively involved in legacy BlackBerry dev. @daniloercoli do you have an opinion about this?
Support Help
- Support Help – blank. @isaackeyet
XML-RPC & 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. Contributions
I’m not sure what this section was supposed to be about. Maybe we’re talking about native libs that interface with XML-RPC and other APIs? If we’re talking about XML-RPC itself it would belong to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.
General Guides
- General Guides – blank. Should be a short intro.
- Using GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ & TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. – blank.
- Changing Hosts on Mobile Devices using Charles – blank. @beaucollins
- Testing with the pre-flight checklist – blank. @aerych
Credits
- Credits – blank. @isaackeyet
There has been some conversation about the best way to denote a page’s status: drafting, draft, editing. The handbook pages don’t seem to support tags, so I wonder if it would work to just append the status to the title. This way it would at least be easy to see a page’s status at a glance from the admin. Thoughts? If we like this idea I’ll go through and update the page titles for Rachel.