# Do's and Don'ts when developing First Project with Ignition?

**URL:** <https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592>\
**Category:** General Discussion\
**Created:** [July 23, 2024, 8:55am UTC](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592 "2024-07-23T08:55:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![danielps1818](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@danielps1818](https://forum.inductiveautomation.com/u/danielps1818)\
**Post date:** [July 23, 2024, 9:56am UTC](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592/2 "2024-07-23T09:56:14Z")

</div>

Don't be scared of making folders.

In our team we didn't do it until it was too late and we had a tree that looked like this _(and it was hell looking for anything)_:

Scripting  
├ randomfolder  
│ ├ class001  
│ ├ class002  
│ ├ class004  
│ └ class003  
├ randomfolder2  
│ └ class18  
├ class2  
├ class4  
├ class3  
├ class5  
├ class8  
├ class10  
├ class12  
└ class7

Navigation in a project is key to efficiency and organization. Is preferable to have folders than a mess of files.

Also, I really recommend making templates so you could reuse views.

---

_[View the full topic](https://forum.inductiveautomation.com/t/dos-and-donts-when-developing-first-project-with-ignition/93592)._