Good or bad practice, multiple projects (LVProj) in same top level folder

[EduNI]

I am attempting to reorganize my various LabVIEW projects.

I did some searching and found articles on managing projects but none that address multiple projects with shared code. For instance, I found this article it doesn't talk about how to organize multiple projects share common code. Is it good/bad practice to have multiple .lvproj files in the same top-level 'root' folder with common VIs in subfolders?

https://www.ni.com/en/support/documentation/supplemental/08/best-practices-for-managing-ni-labview-a...

Right now I have 3 projects that share common code, mostly as individual VIs, but some classes and libraries too. The 3 projects each have their own top level folder off of the C: drive. My HAL (hardware abstraction) folder is also in a top level folder off of the C: drive. I was considering putting all my lvproj files in the same top level folder off of the C: drive, in something like "C:\Projects" then "C:\Projects\Proj A" , "C:\Projects\ProjB", "C:\Projects\ProjC", and "C:\Projects\HAL".  Is this a good or bad idea, and why? Are there any pitfalls do doing this? Thanks!

[RTSLVU]

Right or wrong I put the .lvprog in the top level of the project folder.

I put VI's that are shared among other projects in a folder in the user.lib directory so they show up on the tools pallet under User Libraries.

[crossrulz]

I have a project for my common libraries in its own repository.  I build those libraries into PPLs.  Then all of my other projects, also in their own repositories, have their own copy of the PPLs that they can use.