improve layout of javascript files/folders to make clear where users are expected to edit things

[gureckis]

currently the src/ directory has lots of .js files only some of which the experiment developer is expected to really edit (e.g., router.js). would make sense to move the files you aren't expected to touch (unless contributing bug fixes/new code to the base project) versus those that almost everyone will need to touch/edit when starting a new project

[gureckis]

Notes from meeting 3/13:

Names for things/restructuring file layout:

All these go in src/user

src/router.js - timeline? Pages? Major user editable (clean it up to remove at the bottom guards setup)
src/icons.js - rarely needs to be editing but maybe worth being in user space
src/App.vue - leave alone

ALL these go in src/internals? src/core?
src/config.js - do we need that to be editable? – they edit env files technically
src/createpinia.js - not user
src/main.js - not user
src/randomization - not user
src/seed - no user
src/subtimeline - not user
src/timeline.js not user
src/utils.js no user
src/stores - nothing user in there really
src/composables - nothing in there for users really

Components:
Internals or core?
1 folder per “page”?
Lib folder for library of common components used several places

Captcha “Route”

[gureckis]

notes today was that we make a src/user folder that contains the task and specific editable things that you might need in your experiment. the other components move to core/components and are named according to the core function. page-level/route-level components will be called Views. so for example InformedConsentView.vue. Might take a docs first approach on explaining this.