Well the simple way is to give the directories meaningful names and to have a text file (readme) in each detailing what that directory is used for and and other pertinent information.
I want something more sophisticated than file names and readme files.
for each project i may have google docs document and other sources i want to link to
I may want to write daily update about the project files, and I want the tool to be integrated in windows explorer
if i have for example recursion of 7 folders and subfolders, it becomes tedious to write readme for each one
I'm currently using git for code versioning. Do you believe it can serve to my purpose?
I prefer something integrated in windows explorer ☺
for each project i may have google docs document and other sources i want to link to
it becomes tedious to write readme for each one
Git doesn't care which files you store in your repository. Can be anything, even (large) binary files.
But: It is considered bad practice to commit "build artifacts", i.e. anything that can be generated/derived from source files. Instead of committing build artifacts, commit only the sources and the corresponding build instructions/scripts. For example, do not commit PDF or HTML files; instead commit the Markdown source files, from which the PDF, HTML or whatever can be (re)generated, e.g. via pandoc.
Learning Markdown isn't that difficult, but having an editor that lets you view your Markdown source document as it would appear on your repo host is nice.