Folder structure

[Beanow]

I think we'll create several categories of artefacts here:

• Research / rationale documents
• Content for the wizard (context, further reading, options, outputs)
• Tech and styling of the wizard
• Builds

They will probably have different processes and even #2 licenses tied to them, so I think it would make sense to create a folder structure to reflect this.

Builds may be better placed elsewhere though. The github pages /docs in master feels a little confusing naming wise. Perhaps a gh-pages branch is a good fit here?

[nothingismagick]

Branch is a pain to maintain, in my opinion. Whats wrong with docs?

[Beanow]

If you have a CI build connected to a push to master, it would update /docs on master and trigger another push. Infinite build loop 🚀

Naming wise I was thinking something like this, isn't too intuitive.

wizard
├── content
├── docs
├── research
├── src
├── LICENSE
└── README.md

If docs and src could have a better name here I think the top level is reasonably clear.

[Beanow]

From discord the idea is to use app for the node project instead of src.

wizard
├── app
├── content
├── research
├── LICENSE
└── README.md