> For the complete documentation index, see [llms.txt](https://sygnal.gitbook.io/sygnal-webflow-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sygnal.gitbook.io/sygnal-webflow-components/cc/sygnal-layout/hierarchy.md).

# Hierarchy ✅

### Overview

The **Hierarchy** component transforms a list of items or collection list content into a hierarchy. 

* It's designed for up to 5 levels of hierarchy, each of which;
  * Can be based on a completely different "level" template that you customize 
  * Can be always-expanded, collapsable, or collapsed 
* Source content is simple to manage, a collection with a single ref to itself is adequate- each item identifies its parent. 

Uses; 

* This is ideal for hierarchical navigations. 

Notes;

* Avoid circular references, like B's parent is A, and A's parent is B.  The component will seek to handle that situation but since it presents an undefined data structure, there's no way to handle it "gracefully."  

{% embed url="<https://www.loom.com/share/38acf6fcdcf74e90acb0dd2e35d3b359>" %}

## Examples

{% embed url="<https://webflow-core-component-test.webflow.io/hierarchies>" %}

<figure><img src="/files/4SzAuhG14GKrl9omddBe" alt=""><figcaption></figcaption></figure>

## Component Properties

**To be documented. Use the video as reference for now.** &#x20;

## Variables

Use these for styling;&#x20;

cc-hierarchy-1-border-radius
\
cc-hierarchy-1-border-width
\
cc-hierarchy-1-border-color
\
cc-hierarchy-1-bg-color
\
cc-hierarchy-1-color
\
cc-hierarchy-1-font-family
\
cc-hierarchy-1-font-size
\
cc-hierarchy-1-font-weight
\
cc-hierarchy-1-line-height
\
cc-hierarchy-1-padding-left
\
cc-hierarchy-1-padding-top
\
cc-hierarchy-1-padding-right
\
cc-hierarchy-1-padding-bottom
\
cc-hierarchy-1-icon-color
\
cc-hierarchy-1-icon-size
\
cc-hierarchy-gap


---

# 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:

```
GET https://sygnal.gitbook.io/sygnal-webflow-components/cc/sygnal-layout/hierarchy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.