Sigil definitely needs some documentation. Although an offline version should be available and is planned, IMO the best documentation is always online since it can be updated even between releases. Google code provides all projects with wiki pages. Sigil's pages can be found here (there is not much there now).

I'd like members of the MobileRead community to help write some docs for Sigil: best practices, guides on getting things done, etc. Whatever you think is necessary. The reasons why I'm asking for community help follow:

The more time I spend writing docs, the less time I spend writing code;

The community has already produced some wonderfull guides and tutorials for various tools, including other ebook editors;

People who want to contribute to the project but don't know how to code now have a way of helping out.

Anyone interested can respond here and I'll add them as contributors to Sigil on it's project page. You'll need a Google account.

I'd like the documentation to be written in reStructuredText, and then handed off to Sphinx which will then generate an epub and a nice PDF version with LaTeX (yes, PDF for technical documentation is preferable over epub).

But someone has to write the RST docs. I intend to write some/most/all of it depending on the number of volunteers. But I've said it before, and I'll say it again, the more time I spend writing docs is the less time I spend writing code.

The 0.2.0 interface is here to stay and no major redesigns are in the foreseeable future, so there's a relatively stable basis from which to work.

Anyone willing should post here, send me a PM, an email, whatever. Just get in contact.