Michael Priestley's blog
I attended several sessions on metrics, including the conference keynote, and a few key points jumped out at me:
The wrong metrics can be worse than no metrics at all
Metrics should be stable over time to allow for tracking
Start by figuring out what decisions you need to make – then gather the metrics you need to make that decision
Two weeks after the fact, I'm still processing stuff I learned at the conference. Over two and a half days with four tracks of presentations, there wasn't a single hour when I didn't want to be in at least two places at once.
I'm told there were over 350 attendees from 17 countries around the world, many of them new to DITA. The conference provided incredible depth of technical content, but will definitely need more introductory sessions or workshops next year as well to balance things out. The community is growing!
The lightweight DITA proposal for DITA 1.3 is starting to come together. The proposal responds to requirements from the community for a lightweight version of DITA to ease adoption by groups who don't need all the features of full DITA.
A very interesting first day. Some quick notes:
This article got published on developerWorks last month:
This should be of interest to anyone who has generated Javadoc in the past but wished they could get a more semantic, reprocessable format output instead. The doclet produces content using the DITA API specialization, which can be processed with the DITA Open Toolkit. Note that it includes the actual doclet code in the resources section, so you can try this yourself at home.