# Fold in (Hide) part of the interface

**URL:** <https://forum.netlogo.org/t/fold-in-hide-part-of-the-interface/794>\
**Category:** Feature Requests\
**Created:** [April 17, 2026, 1:50pm UTC](https://forum.netlogo.org/t/fold-in-hide-part-of-the-interface/794 "2026-04-17T13:50:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![janlo](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/j/f08c70/32.png) [@janlo](https://forum.netlogo.org/u/janlo)\
**Post date:** [April 17, 2026, 1:50pm UTC](https://forum.netlogo.org/t/fold-in-hide-part-of-the-interface/794/1 "2026-04-17T13:50:04Z")

</div>

When building models, I start simple and get simple models. Because of various reasons, I add more and more controls for visualization or substantively extend my models. Later, I try to group controls into things relevant at setup, things relevant at runtime, just visualization-relevant controls, and model extensions. It becomes super large. Still good for me, but it loses its simplicity for educational purposes and can overwhelm new users with too many options. I think in the end it is a fundamental design problem with no standard solution. Still, the option to hide a certain part of controls and outputs would give an option to design a better learning path by focusing the user first on the essential things before “opening” advanced visualizations and model extensions.

---

<div class="post-metadata">

**Author:** ![jzkelter](https://forum.netlogo.org/letter_avatar_proxy/v4/letter/j/a5b964/32.png) [@jzkelter](https://forum.netlogo.org/u/jzkelter)\
**Post date:** [April 20, 2026, 10:08pm UTC](https://forum.netlogo.org/t/fold-in-hide-part-of-the-interface/794/2 "2026-04-20T22:08:15Z")

</div>

Thanks for the suggestion, I’ve wanted something like this as well!