<p>Most of our websites use a main structure for the page tree. In some cases, those structures can become quite large and entries further down are not shown initially without scrolling down/autoloading. This is annoying, especially it has to be done again and again when you reopen the structure overview.</p>
<p>For me some changes / additions could improve the situation:</p>
<ul>
<li>Have a setting that forces only level 1 entries to be shown, the others are closed.</li>
<li>Alternatively have a button to close all level 2 and deeper subtrees.</li>
<li>and maybe remember search terms when leaving the overview and coming back.</li>
</ul>
<p>What are your thoughts on this?</p>

CC BY-SA 4.0
2020-10-22T19:54:45.497Z
Not sure if this is a question or a feature suggestion? Feel free to look for a relevant issue at Craft's [issue tracker](https://github.com/craftcms/cms/issues) or raise a new issue.
RitterKnight
CC BY-SA 4.0
2020-10-23T06:13:26.447Z
a question: I wanted to find out if others share the same problem and what they think about my ideas. afterwards of course an FR.
Matthias Redl-Mann
<structure><user-interface>
Alternative overview for structures
# Alternative overview for structures

(Asked by: username_0 on 2020-10-22)

Most of our websites use a main structure for the page tree. In some cases, those structures can become quite large and entries further down are not shown initially without scrolling down/autoloading. This is annoying, especially it has to be done again and again when you reopen the structure overview.

For me some changes / additions could improve the situation:

* Have a setting that forces only level 1 entries to be shown, the others are closed.
* Alternatively have a button to close all level 2 and deeper subtrees.
* and maybe remember search terms when leaving the overview and coming back.

What are your thoughts on this?

**Tags:** structure, user-interface
> **Comments:**
> **username_1**: Not sure if this is a question or a feature suggestion? Feel free to look for a relevant issue at Craft's [issue tracker](https://github.com/craftcms/cms/issues) or raise a new issue.  
> **username_0**: a question: I wanted to find out if others share the same problem and what they think about my ideas. afterwards of course an FR.  

---

## 0 answers

