> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/user-guides/holoplot-system-design.md). # HOLOPLOT system design Learn the specifics of designing with HOLOPLOT systems and beams, including how to control and shape sound patterns for optimal effects In this guide, you will learn the specifics of designing with HOLOPLOT systems and beams, including how to control and shape sound patterns for optimal effects. You will discover the different types of beams available and learn how to use them to achieve the best results in your projects. Jump to any of the steps or click on the next section at the bottom of this page.


System design best practices	This resource provides the essential principles and key considerations for effectively integrating HOLOPLOT systems into your projects.		MasjidMisr_ArrayPositioning_3840x2160.png	System design best practices
Beam design best practices	Learn about the different types of beams available, their applications, and the detailed design process.		MCIC_Beams_Dome.png	Beam design best practices

--- # 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://docs.holoplot.com/user-guides/holoplot-system-design.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.