4 ms·
I use a system I created called: Shelf, Desktop, Cabinet. I use the 'shelf' folder to store all the files I use and reuse (usually, transform) at work. E.g. te
by rodolphoarruda 6y ago
I use a system I created called: Shelf, Desktop, Cabinet.
I use the 'shelf' folder to store all the files I use and reuse (usually, transform) at work. E.g. templates, stock photos, contracts, pieces of code etc.
My actual projects are sub-folders inside the 'desktop' folder. Metaphorically speaking, they are 'sitting on the desktop'. Folders are named like this: 'client_name - project_name'. Whereas 'client' can be anything like: 'me - learning Vue.js'
The 'cabinet' folder files completed projects should be no longer on my 'desktop'. I just move them into there, where they can be easily sorted alphabetically. But before doing that, I take elements that could be reused someday in similar projects, copy them into the 'shelf' folder and give them a generic name that I can easily find through a search.
edit: clarity (I guess...)
- raindropm 6y agoSimilar to mine too. Though my 'Desktop' is my Google Drive folder, always sync to cloud. My real desktop though, is temporary place for pile of files of current working project of that day. I clean up this real desktop at the end of the day, put the files into their rightful place or delete it, just some old habit. I have some kind of 'shelf' too, but your idea about taking element from soon-to-archive project and put it in a shelf is what I overlook. I'll give it a try!
- rodolphoarruda 6y agoIt can be hard to separate things in the beginning because if you ask yourself: "What is important from this work that should be in shelf?", your answer would tend to be "everything". So, instead, you should be asking yourself "which elements can I be reusing in future work?" regardless of their importance.