Problem: There are generally many examples of using batch (and bash) scripts in DOS shell to automate various programs. But I have found few resources that suggest ways to manage all the batch files that can compile in a project, or over the years. (Or perhaps I have just been using the wrong keywords for searching).
Background: I have never actually attempted to really organize batch files I've made so that they can easily be reused. Currently I have various bat files in folders that I modify with txt editor (if I can manage to put them in a place that I can later remember). Before I put effort into a type of organization structure, I want to ask if I am thinking about the problem/potential solution most effectively.
Best general solution?: The general approach I can think of is modifying all batch files to accept parameters, and then creating interfaces that ask for parameters using either "higher-level" batch files, or creating a GUI that then passes parameters to certain batch files.
Question: Is this approach considered the most common/efficient for batch file organization, or are there some valid alternatives or additions to the approach that would be "better practice" (involving software that automates the process/other ways of organizing batch files for reusability/...)