In my previous post, I got a pretty pointed comment that actually helped me clearly state my goals for my project. I'm going to paste my reply here because I think it's useful to draw my roadmap for you all:

The idea is not to make GNOME help specifically for the phone. GNOME help is generic content for me to work with. My ultimate goal is to create a tool like yelp-build to translate *any* Mallard-formatted documentation into a mobile format. One possible use I can think of for this specific project, however, is a mobile equivalent to a physical manual. One can hold the manual in their hand while using their desktop or laptop, following directions in the help.

More broadly, this will be useful in the short-term for GNOME projects that already have Mallard-formatted help and may in the future transfer to a mobile format (games, music players, chat programs, etc). In the long term, as new GNOME apps specifically made for a touch screen are produced, this could be a counterpart to Yelp in that medium.

Behind each of the bare-bones one-screen UIs was a pretty intense analysis of content and structure, as well as some time to familiarize or re-familiarize myself with the structure and code needed. They represent two major projects: 

* The first (duckling) is mobile app written in Java with an XML UI specifically for Android that will run as a standalone port of Yelp. 

* The second (gnome-help-mobile) is a mobile website written with HTML, CSS, and Javascript, Along with it is the tool that takes .page files written in Mallard and translates them to the completed mobile site.

The first of these two is on the back burner, but I will return to it. It is easier and more relevant to produce the second right now.

Since moving content and applications into a touch-screen environment is vital to staying relevant, I believe it is important to start building the infrastructure for a documentation system commensurate with this movement.

Hope that clears some things up, keep the constructive criticism coming! :)