I'm looking for advice on how to structure folders for a script project I'm updating. I've been maintaining a ping script for my team, currently organized within SharePoint, but I'm unsure of the best practices for arranging my project. Here's a glimpse at my current structure:
ROOT - Ping Suite v.1
- Core
- Run Me.ps1
- Readme.txt
- Layers
- Input
- individual input functions files
- Processing
- individual processing functions files
- Output
- individual output functions files
- Logs
- Resources
- Icons
- Icons for gui
- Master
- Master Devices.xlsx
- Xaml
- gui.xaml
- Exports
I want to become a better script writer and improve how I organize my projects. I haven't been using GitHub due to security concerns about sharing company information. Any tips or best practices would be greatly appreciated!
1 Answer
It looks like you might benefit from putting your input, processing, and output function files into separate modules. This way, your code will be better organized and easier to manage. Just keep the module in the same folder that users download from, and they can import it into the main script easily.
Interesting! So once I have the module in place, users just need to call it in their scripts, right?