Thanks for all the comments lately. Keep them coming. A combination of site stats and comments shows that there is a steady stream of interest in this topic.
The current priority is to create a decent introductory tutorial to help people get started – the Cookbook isn’t much use if you can’t get started and there is a serious lack of good basic-level tutorials in the community. However, much of the content is added when I have to find something out, which is why the Cookbook tends to be updated more often.
There is a reality check that I’m massively resource constrained at the moment, so keep your fingers crossed that I get appropriately distracted one weekend to make some decent progress.
I haven’t had much time to review the project’s current status, but the areas that currently come to mind include:
Introductory Tutorial to Python UNO
As I’m getting better at using Python with LibreOffice, I’m getting more qualified to write an introductory tutorial! Some of the methods that I used to start with probably weren’t the best ones, so in some respects, it’s probably best I didn’t write this section first. However, it clearly is the most useful part to the wider community.
Uploading Source Documents and Processing Code to Github
The current version is created by processing an ODT file to remove comments, empty sections etc. This means there are two useful things straight-off: a nice big ODT file for people to experiment with, and some sample code. Uploading them to Github would not only give people access to them, but would also allow external contributions.
Better Website and Online Readable Version to Allow Easier Discovery, Browsing and Comments
I don’t think that a super-flashy website is a great priority, but I think it would be good to create an online-viewable version partly to help people find the content on search engines and browse it more casually. It would also provide an interface for submitting comments next to items within the document. In my day-to-day work I have recently been developing a website using Twitter Bootstrap, and I quite like the style of their documentation browser, with a the sidebar navigation. This would also provide some good example code of converting ODT to HTML.
Bug Identification and Fixing
I get quite a lot of crashes (and they really annoy me!). Bulk processing a wide variety of documents inevitably leads to finding more edge cases. I’d like to explore finding a way to better work with the LibreOffice developers to get bugs identified and fixed. I think my time is better spent working on documentation, so it’s about exploring ideas like making a test environment that works for tutorials and Python UNO newbies, and which provides useful tests for LibreOffice developers which they can use independently.
More Sample Code
Most of the code that I write for my own projects could be published for people to look at, complete with some test files to allow easy experimentation. It just requires me to do a bit of work checking there is nothing sensitive included, and separating out configuration from the actual processing code. It’s not necessarily “good” code, but it could still be helpful.
As per usual, comments are more than welcome on what I should spend my time working on.