First pass (-- HilaryHolz - 30 May 2008)

This needs to expand into a discussion of the leaf, node and root info architecture for related materials.

It should link back to the sense-making content model, and up to interaction design. But for right now I'm just going to link in the existing template topics so others can start using them.

The template topics currently exist only (?) in the LabBestPractices? subweb. To have them show up in the new topic form, you need to add the template topic to the subweb in question (I think - I don't think it is enough to have them in the underlying web, haven't had a chance to explore yet). Then they show up as a choice.

• leaf template - LeafTopicTemplate
• node template - NodeTopicTemplate
• root template - to be written

Questions:

• How to manage ToDos? Answer - see the To Do topic, wasn't very useful until it was in the Ahat/AhatTWiki.WebLinks component, which is part of the 'within this web' in 'selected topics' in v0.02 of Ahat/AhatTWiki.AhatSkin.
• How to manage LabBestPractices? ?

After having lived with the above for a bit (-- HilaryHolz - 15 Jul 2008)

The issue with template topics and visibility in various webs and subwebs is really a twiki implementation question. If template topics weren't stored as flat text files, it wouldn't be an issue at all, you could just specify where in the hierarchy the template topics would be visible. We can probably address that in some reasonable clean and clever way. In any case, we shouldn't let implementation issues get in the way of conceptual design. We are interested in user experience and sense-making, not technology-driven deployment.

I created a template topic to model access controls to restrict access to topics. Charles is starting work on organizing the materials in the MPDL web, and it seemed like a useful template. I decided that I wanted to start him thinking about templates in the process of organizing, since he is very visual, and has a knack for that kind of thing. More as we go.

Starting to sort out different perspectives on info architecture

[... Discuss new versions of templates and support for same, e.g., TWikiForms? , possible custom taghandlers... re: Users as Research Inventions, but TWiki Design also excellent in that it is highly orthogonal. What is missing is the translation in the form of illustrative examples, experiential learning. ...]