Forking this repo into multiple projects

[markdav-is]

Over time this repo has become the working folder for a few experiments and abandoned efforts. I'm proposing forking this repo into it constituent projects that are easier for someone to pull-and-build without trying to navigate the mysteries of extra folders and parallel efforts.

One fork would be the existing production site at http://littlehelpbook.com that is written in dotnet. We could call this simply little-help-book or little-help-book-dotnet or little-help-book-api

there are other projects as well that might want to be broken out.

I'll do this eventually on my own, but it's worth having a discussion, so we can coordinate. once the fork happens, we can remove the sub-projects from the legacy repo.

[ArthurSmid]

This is a good idea—definitely will make it easier for people who are new to the project to begin volunteering if all of the issues listed are specific to one repo.

Anything you need for the coordination, please let us know, maybe linking this to our Slack channel for the project. It's possible that people read that more than the Discussion feature here.

[markdav-is]

it depends on the what you consider forks and what you consider the origin. If you want to fork little-help-book-web into little-help-book-js and leave the C# code in little-help-book-web then there is nothing for me to do. If you want to keep the table-of-contents-style-homepage in little-help-book-web and fork the C# code, I can fork the repo to keep the C# stuff in another repo.

[markdav-is]

the API was forked to https://github.com/OpenEugene/little-help-book-api

[ArthurSmid]

Nice!