Document reorganization

[CBroz1]

Thanks for collecting these materials! My way of 'reading' is to reorganize. I used some tools to standardize document layout (e.g., pre-commit, markdownlint) and divided information info subfolders in a way that I think will be helpful for others. If this doesn't align with your goals for the repository, I'm happy to provide more detail on the tools, revise or close the PR.

Cheer!

[cognitivetech]

wow! this is great. I haven't had such a comprehensive contribution, before. will take a moment to review.

looks like you've mostly re-organized. I also enjoy organizing content.

One thing I'm a little confused is where a long quote on only 1 line is turned into a many lined quote, defining the width of output.

I will look closer at your revised README, its hard to evaluate such a large contribution :)

Not sure what I should do with these contents.. probably just leave them here for other students or for content creators to use as a foundation. But maybe I will turn it into a website sometime. With LLM could go far in creating original content about NVC... We'll see. :)

[CBroz1]

Sure, take your time, no rush.

1. Why turn a long quote into multi-lines? This rewrapping process is a convention established by markdownlint and other opinionated markdown formatters. While not required, it makes future diffs easier to visualize. My personal preference is because I read in a terminal window. This could pretty easily be reverted by changing some settings in the .yaml files. Please let me know if you have an opinion one way or the other.
2. The process of turning a github repository into a website is pretty easy with tools like mkdocs. For example, I use this repo to manage my cookbook website. I could put together the same for this repo pretty easily, but launching the site would require either some minor work on your end, or granting me admin permissions. The url could be cognitivetech.github.io/NVC. Lmk

[CBroz1]

Closing due to inactivity. Feel free to reopen