refactor: PE-411 repository structure should be reorganized to make initial impression simple

jdmedlin1 commented 3 months ago

📝 Description

The current layout of the repository is not friendly for newcomers; having all templates, examples, configs, etc. thrown at the user at once.

I propose we categorize the projects into their respective directories for the sake of simplifying the variance of types of info at once. Templates and examples should be put in their own repositories.

With this change, we will need to adjust npm scripts to point to the same projects. Additionally, we will need to give each new directory its own README as defined in https://brightsign.atlassian.net/browse/PE-410

📋 List of Changes

Please provide a concise list of the main changes.

🧪 Steps to Test

Step 1

Notes to the Reviewer

📸 Screenshots

✔️ Dev Complete Checklist

[ ] PR template filled out
[ ] Change is tested by submitter
[ ] PR follows all linting and coding standards
[ ] Github Issue exists (if applicable)
[ ] Team member has been assigned
[ ] At least one commit message is in Conventional Commit format

bhastings1019 commented 2 months ago

Is this Draft PR ready for review?

bhastings1019 commented 2 months ago

The root README may benefit from refining the written form to present HTML (JavaScript) or Node Application, with direct links to each near the top.

We'll look back over some of these READMEs

jdmedlin1 commented 2 months ago

Just need a reapproval on this since GitHub is blocking it.

brightsign / dev-cookbook