I'm going to preface my comments by warning you that I'm going to provide alot of noob feedback here, and some of it may sound critical. Take it as a fresh perspective and take the best and ignore the rest! But I also want to say thanks a million too, because without this site I would have abandoned K2 already.
Templates?
I found the "91-templating" doc you mentioned and was able to get a new K2 "template" to show up in the category drop down list. However, I'm not sure you can truly call that a template, since the scheme you described doesn't include any css. I haven't yet looked into the css 4 k2 tool you mentioned, but it sounds like it may be necessary to create a complete template for K2. In fact, in my case that tool may be all I need.
Functional K2
At this stage of my development I'm just looking to get functional content into K2, and I believe I can do that through the k2.css alone. My issues deal primarily with text visibility. I say K2 isn't functional but that's just because there's a conflict between the K2 foreground / background and that of the Artisteer template.
Dark or Light Text "conflict"
It may very well be that the color of an item's title, which is inherited from the Joomla template and not specified in k2.css is the same color as the (block) background which is defined in the k2.css file, therefore rendering the title text invisible. I suspect that type of conflict has a high degree of probability of occurring, especially if the joomla template has a dark tone or background. Is it even possible for a K2 template to be designed such that it doesn't know or care about foreground & background colors of the Joomla template it inherits values from?
Similar problems arise within joomla itself, such as white text for a dark background that can't be seen in the article editor without changing the editor configuration to provide a dark background. Fortunately that capability is available.
Template Expectations
I also read your article about template expectations (
simon.getk2.org/blog/item/422-k2-templates-the-expectation-a...) and was surprised by the lack of details there.
To be fair the purpose of that article seemed to be explaining how joomla templates and K2 templates are totally separate and segregated beasts and therefore they are inherently "compatible". However, I can tell you from first hand experience that is a bit of an oversimplification.
What is Compatibility?
There are several things to consider in determining template compatibility in addition to structure. Perhaps it's all in the word "compatible", but I'll bet many people expect turn-key compatibility where such issues are handled by Joomla or K2.
It would be nice if K2 was structured such that templates were fully encapsulated, including an xml file etc so it could be installed like any other joomla extention. From what I can tell a K2 template must be "placed" in the correct location by ftp or other direct file insertion method.
My Expectations
When I installed K2 I had a site template I was fairly happy with and I wanted to add K2's functionality. However I discovered I needed to redesign the k2.css to make it work (mainly to resolve the invisible text problems due to foreground and background choices in the 2 templates). And that is a time consuming and tedious task as it stands today.
As I read the "expectations" article it sounded to me like people didn't expect to work through all the detailed tweeks as I am doing, which seem to arise as a side affect of choosing a dark background color scheme.