- Implementation guide
- Rich Internet Applications: AJAX, Flash and DHTML
- Coding standards and Best Practices
- HBX to SiteCatalyst Migration
It's a toolkit, not a templateAs a senior architect I often had to contribute to business requirements, functional specs and implementation guidelines. After a while, writing a new document is a matter of stitching already well written sections, adjusting a couple of words here and there and making slight contextual adaptations. I think the toolkit is exactly that: experience from the field; tips & tricks gathered and structured in a set of documents. However, it's made for people who know what they are talking about, neophytes will likely get lost.
Don't expect a "template" for defining your process, KPIs, dashboards, custom metrics & reports or a special magic recipe to do your implementation. The toolkit should really be viewed as a quicker way to gain the knowledge others have taken months to learn. That's where the value is.