Hi,

This is key for me - the developer guide will be a collection of documents that should each be easy to navigate. The idea of "neighbours" to docs is vital - and one of the reasons I hope to see any PDF documents made available as HTML so that we can send people transversally from API documentation of widgets to code samples using them to technical guides of the APIs to UI guidelines and best practices the author should bear in mind when developing.

There are very few developer docs which you read like a novel - the only one I can think of is "getting started" - how to get going as a developer, and what are the basics you need to know. The rest is a network of searchable interconnected material.

Perhaps there has been too much focus on native application development in the wiki. Perhaps the lack of focus on Qt Creator & similar tools is because people aren't using them much yet? We don't know exactly what's going to be available for Maemo 6 so coming up with a table of contents for web APIs and Qt 4.6 is a little tricky.

How about having a "Hello World in 60 minutes" chapter which explains the differences between the various development environments and goes through the hello world process for each (web widget, Qt native app, maybe Hildon native app) as the first chapter?

After that, we can have an overview of Maemo, more in-depth overviews of tools, environments & available APIs on the platform. What's vital is getting someone to the stage where they feel they have accomplished something as quickly as possible.

Dave.