Folder Tree.

[sepulchra]

My work often has me creating lots of repetitive folder trees for projects and they tend to be cyclical, so I usually make a template and keep making the same project folder trees for months. Over the years I’ve attempted making these in a variety of ways. This started with Automator and then getting help to implement in alfred back in 2018.  I then also saw this recent workflow shared, and I remembered I had created something similar by just using automation tasks and no external dependencies.

 

 

I owe most of this workflow’s setup to some of that early experimentation and @Stephen_C's experimentation on his folder workflows.

 

I’d figured I would share and see if would be useful to others and if there might be some helpful tweaks I could make. I’m not so sold on the icon yet. Also @vitor I would love for you to weigh in as you also seem to find useful tweak or efficiency. Here is the tree: https://transfer.sh/62F5tkcvDU/Folder Tree TEMPLATE.alfredworkflow

 

I do wonder if this has any practical purpose beyond being an example? In it's current form, users could use it as a template but would need to set the argument to their custom folder paths.

 

Thanks!

Edited October 15, 2023 by sepulchra

[vitor]

Three tips:

• If you intend to share it with more people, you should use GitHub or something like that, as transfer.sh only lasts a few days.
• The Universal Action might be better as a File Action limited to only folders.
• Instead of multiple Arg and Vars at the end, use just one with one path per line. Then connect it to a Split Arg.
  

[sepulchra]

Thanks @vitor. That is much much cleaner and instructive. I didn't put it on github as I didn't know if it would be of value beyond being an example to the wider community. In essence everytime i start a new project with its own set of folders, I would replicate this and created the specific folder paths etc. Look how much cleaner this looks:

 

I never have used the split argument object and it works as I have configured it, but is this how it "should" be?

[TomBenz]

10 hours ago, sepulchra said:

Thanks @vitor. That is much much cleaner and instructive. I didn't put it on github as I didn't know if it would be of value beyond being an example to the wider community. In essence everytime i start a new project with its own set of folders, I would replicate this and created the specific folder paths etc. Look how much cleaner this looks:

 

I never have used the split argument object and it works as I have configured it, but is this how it "should" be?

Pls share updated version via Github. Many thanks in advance

[vitor]

13 hours ago, sepulchra said:

but is this how it "should" be?

 

Yes, that’s perfect. You don’t need two of them, though, both streams can connect to the same one.

[sepulchra]

Thanks so much. This has been super helpful.