# Structuring larger projects

**URL:** https://discourse.nodered.org/t/structuring-larger-projects/63288
**Category:** General
**Created:** [31 May 2022 09:21 UTC](https://discourse.nodered.org/t/structuring-larger-projects/63288 "2022-05-31T09:21:40Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [31 May 2022 22:55 UTC](https://discourse.nodered.org/t/structuring-larger-projects/63288/5 "2022-05-31T22:55:51Z")

</div>

> [@cerietke](#):
>
> Agreed on partitioning the flows, but that's kinda where I run into challenges. In traditional programming I can essentially create as many levels in a hierarchy as I need, but in Node-RED it's essentially limited to flows, subflows and perhaps groups (thanks for mentioning those, I should check that out). As such I don't really have as many hierarchical levels as I would like

You should checkout the link call. I find it more manageable than subflow & they can be easily linked and nested.

Here is a basic example: [Feasibility of implementing functional operators without javascript - #8 by Steve-Mcl](https://discourse.nodered.org/t/feasibility-of-implementing-functional-operators-without-javascript/62361/8)

---

_[View the full topic](https://discourse.nodered.org/t/structuring-larger-projects/63288)._