I recently completed all the projects and earned the Full Stack Certificate.
I’m now cleaning up the little bugs I’m my projects and giving them my own style so that I can use them in my portfolio.
Part of this process is pushing the projects to GitHub. Should I create a new repository for each project? Or should I, for example, put all the D3 projects in one repo as orphan branches? I’ve read some info on the pros and cons of multirepo vs monorepo. But it didn’t really settle the issue for me.
Is there any reason not to create a new repo for each project? Other than I’ll end up with a bunch of repos?
Thanks for the response, that is what I was planning to do. But then I started reading about people advocating for monorepos, however that is probably not relevant to my particular situation.
If you have time, it can help to flesh out your readmes as well to give a description of the project, how to spin it up locally, and even some screenshots.
I would only recommend a mono-repo approach for personal projects if you plan on sharing code between the projects, or if each project “relies” on other projects.
If you don’t need or want these, having a project in their own repo is perfectly fine to keep things focused, isolated, and easier to understand. Plus re-doing some boilerplate here and there will probably teach you more than having to deal with 1 git repo all the time.
Situations like a full-stack app could be done in a “mono-repo” where you have the client-side, back-end, utility scripts, and shared code all in 1 repo, even though you could throw them into their own repo.
Finally, there is nothing wrong with putting all your projects in 1 repo just so its easier to show off, but thats more of a personal preference thing, not a technical reason.
