> For the complete documentation index, see [llms.txt](https://garden.urbancolab.design/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://garden.urbancolab.design/introduction.md). # Introduction This is my Digital Garden focused on sharing what I know about the profession of architecture. If you are not aware of the concept of a Digital Garden, I will expand on that as this space grows. In a nutshell, I look forward to sharing my experiences, thoughts, and interests in and around the profession of architecture. I feel awakened by the potential of what a Digital Garden can do to help me spread knowledge and use what is called Public Learning to sow the seeds that others will germinate and ultimately create fruit for future architects that then can sow new seeds and continue the process. If you want me to expand on any of the subjects in this Digital Garden feel free to connect with me on [Twitter @kurtneiswender ](https://twitter.com/kurtneiswender)or visit my business website to see more of my project work at [urbancolab.design](https://urbancolab.design). --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://garden.urbancolab.design/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.