> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/shop-accessories/2026-field-elements/assembly-instructions/getting-started.md). # Getting Started ## Assembly Prep Refer back to the [Kit Contents](/welcome/shop-accessories/2026-field-elements/general-info/kit-contents.md) page to ensure that all necessary parts are located before starting assembly steps. ## Key Assembly Instructions The following pages cover the basic assembly instructions for the a2026 WCP Field Elements
Cover image
2026 Bump (Half)Assembly Instructions2026 Bump - Cover.svgBump
2026 Trench (Fixed Side)Assembly InstructionsTrench - Cover.svgTrench
2026 Net StructureAssembly InstructionsNet Structure - Cover.svgNet Structure
2026 TowerAssembly InstructionsTower - Cover .svgFull Tower
2026 Standalone TowerAssembly InstructionsStandalone Tower - Cover.pngStandalone Tower
2026 Hub FunnelAssembly InstructionsHub Funnel - Cover.svgHub
--- # 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.wcproducts.com/welcome/shop-accessories/2026-field-elements/assembly-instructions/getting-started.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.