Organize repo by unflattening current folder structure

[Botmasher]

The current flat structure is getting a bit unwieldy even at the current size. The unwieldiness will grow with the planned addition of tools/utils, potential topics and scripts, plus any future project files that may get kept here (currently stored locally). First let's outline the problem. Here are the initial questions that come to mind:

1. What does our structure need to account for?
2. What type/strategy of structure do we want to go with?
3. What naming conventions will we adopt and why?

[JessRudder]

I'm mostly working on the script side right now and here are a few thoughts about stages:

1 - complete idea gen (usually a file that has multiple ideas written down)
2 - research (traditionally these usually turn into full scripts, but, I'm getting better about researching and abandoning if I don't think there's a story of interest in there)
3 - scripts (full on scripts that get turned into videos)

Not sure if it makes more sense to have a different top-level folder for each stage, a top-level 'scripts' folder with different folders for "ideas", "drafts", "filmable" or a single scripts folder on the top-level with everything in a single level inside (but namespaced with filename prefixes).

I don't necessarily like deep nesting but 2 deep probably isn't horrible.

[Botmasher]

Riffing on your breakdown, what about a folder for the ideas and ideation processes ./ideas, one for any automated workflow (./tools or ./utils) and then a folder for each project? It'd be nice to separate out scripts, outlines, research, reference art, asset lists for each project. This could also be a top level "reference" folder (or better name)?