Return to GuidanceExplorer

---

Offline Client

* How to filter categories based on topic?
* How to indicate status between BETA, Release, Community Release?
* How to design off-line cache?

Engineering Practices
* How to compose modules for security engineering?
* How to compose modules for performance engineering?

---

Guidance Feeds

* How to limit feed amounts?

---

VS.NET Add-In

* How to associate per user guidance to a project?
* How to associate team guidance to a project?
* How to create content that surfaces in VS.NET?

---

Authoring

---

DFO

* I can't include links between topics or images/schematics/diagrams.
* The templates are also quite different from the document format. This will mean a quite different approach to creating content from that we started out on with the Health Modeling doc.
* It will also remove the sense of progression through the topics unless I create a new category and preserve the topic structure as subfolders. Do we want to create a "Design For Operations" topic and build the topics within this in line with the twelve topic areas we originally outlined? Or should we merge them into the existing topics based on their content.

---

Web Services Patterns

* For content in existing templates, problem in converting to usable Word doc format for porting to GE.

---

VSTS UE

* I still think there’s value in separating content from presentation. Remember that HTML is the hack for SGML, and CSS is the hack to make HTML presentation easier. Consider a longer-term vision of creating single-source content to display on Windows, Web and device. Topics void of presentation markup would be smaller and permit better machine understanding of their contents.

---

Return to GuidanceExplorer