> For the complete documentation index, see [llms.txt](https://evomimic.gitbook.io/map-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evomimic.gitbook.io/map-book/dahn-human-experience-of-the-map/dahn-visualizers.md). # DAHN Visualizers {% hint style="info" %} The difference between theory and practice is smaller in theory than it is in practice. {% endhint %} As noted in the previous section, DAHN visualizers come in the following flavors: * ***Canvas Visualizers*** * ***Action Visualizers*** * ***Node*** ***Visualizers*** * ***Property Visualizers*** * ***Graph Visualizers*** * ***Collection Visualizers*** This section offers descriptions and examples of each. This section comes with many caveats. * In my experience, the best approach to creating a compelling human experience is to evolve it in agile fashion through a series of small iterations with lots of live testing feedback. I am not following that wisdom here. At best, this section presents a *theory* of how an open-ended, dynamic, adaptive human experience of the MAP could evolve. See quote above. * Although grounded in proven patterns and available technology, DAHN combines them in novel and untested ways. It should be treated as preliminary and subject to change as the concept is implemented and refined. I expect many changes, both major and minor, to emerge from these implementations. * The visual examples included in this section are very crude and intended only to convey a tangible sense of the concepts being discussed. Those with any sense of aesthetics or true Human Experience design skills will, in all likelihood, find much that grates against their sensibilities. I ask your forgiveness and, even better, your help. Clearly I need it! But, in a sense, that is what the MAP is all about. As human beings we are all endowed with both gifts blindspots, strengths and weaknesses. The MAP encourages everyone to give creative expression to their gifts in a co-creative mashup dance for the benefit of all. * The pages within this section are intended to serve as a basis for implementation. As such, they include more detail than the average reader may care about. Furthermore, what is novel about DAHN is the adaptive, open-ended, crowd-sourced process through which it evolves. The inclusion of mock-ups may give the sense that these mock-ups define THE (fixed) human experience of the MAP. It is more accurate to think of them as merely the very early seeds into the evolutionary process through which the MAP human experience will unfold. **Copyright (c) 2022, this book is offered to the world under Creative Commons license** [**CC BY-NC-SA 4.0**](https://creativecommons.org/licenses/by-nc-sa/4.0/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://evomimic.gitbook.io/map-book/dahn-human-experience-of-the-map/dahn-visualizers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.