> For the complete documentation index, see [llms.txt](https://help.are.na/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.are.na/docs/getting-started/connections.md). # Connections Linking collections of material Connections are what join channels and blocks to each other. On Are.na, there is no such thing as a "like" or a "favorite", instead we have connections. When you're traversing Are.na and you find something that would fit into one of your channels, hit "Connect". ### Connecting blocks {% embed url="" %} ### Connecting channels You can also connect channels to other channels. To do this, use the "Connect" button on a channel thumbnail (the square icon that you see in a grid) or in the "This channel appears in" section of the channel header. {% embed url="" %} ### Traversing connections Navigating across Are.na and finding content that is interesting to you is all about traversing connections. Hovering connections brings up a mini-preview of the channel, which can help you decide whether or not you want to go down a path. Use your intuition and let it lead you! After all, every connection was made by a human, connections are paths we lay out for each other. {% embed url="" %} --- # 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://help.are.na/docs/getting-started/connections.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.