|
I did a quick run through of estimating the work involved and it makes no sense at this time to do a custom iPad version (or tablet in general) until the template and stylesheets are refactored and cleaned up.
Just some notes for whoever does further iPad style work:
- Due to the way we construct the manual site it doesn't make sense to create a cacheable version of the manual using a manifest. The manifest needs to list all of the files, however all of our references are to directory paths (eg, href="/manual/administration/" will not load /manual/administration/index.html from the cache but instead will try to go to the website.
- if at some point the manifest method is used, need to include the commit or something in the manifest file so that the content is refreshed on new publications
- also the manifest file must be served with MIME type text/cache-manifest. Suggest creating a separate page with <html manifest="mongodb-manual.manifest"> which is a simple stub page to download and cache the book, rather than pollute all pages with the relevant <link> and <meta> tags.
- the following file should be stashed in the root directory of docs.mongodb.org:
apple-touch-icon.png - at minimum
|
- can alternately add icons for different resolution but these need to be specified in every page in <link> elements
- if the docs are published via iBooks we can get a "smart banner" to link to the ibook by using <meta name="apple-itunes-app" content="app-id=<app id>"> where app id is the application id of the ibook.
|