# Inheritance project naming

**URL:** <https://forum.inductiveautomation.com/t/inheritance-project-naming/93694>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 24, 2024, 7:05pm UTC](https://forum.inductiveautomation.com/t/inheritance-project-naming/93694 "2024-07-24T19:05:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 24, 2024, 7:10pm UTC](https://forum.inductiveautomation.com/t/inheritance-project-naming/93694/2 "2024-07-24T19:10:25Z")

</div>

My recommendations are here:

> [@Where do/should Gateway Scripts live with respect to an inherited project structure?](https://forum.inductiveautomation.com/t/where-do-should-gateway-scripts-live-with-respect-to-an-inherited-project-structure/83460/3):
>
> Put all of the logic in project library scripts, in the "universe" project at the root of your hierarchy, if you must. Then, in leaf projects, use one-line calls to the appropriate logic from event scripts and message handlers. (I don't agree with your desire, but this is what you must do to achieve it.) I recommend you not put all your scripts (eggs) in one inheritable project (basket). I recommend a hierarchy something like this: universe ├bg\_common │├gsp │├background1 │├background2 │└we…

{ Worth reviewing the whole topic. }

---

_[View the full topic](https://forum.inductiveautomation.com/t/inheritance-project-naming/93694)._