Nested folders for organisation

Hi TextBlaze Team,
A feature request: For organisational purposes, it would be nice to be able to nest the folders of snippets underneath each other several levels. This way I could have one folder with "Roam Snippets" and another with "Rest of Web". Under the former folder I could then have a series of folders relevant to certain aspects of Roam such as "Template Snippets" and "Organisational Snippets".


@scott - Is there anything planned along these lines?

This would be useful, but no plans for it at the moment. The primary issue is that nesting would complicate the sharing model and how folder settings are applied

For example, if you had folder "ABC" that was shared with and, and it contained folder "XYZ" that was shared with "", what would you expect the permissions to be for snippets in folder XYZ?

Just Or should it be all three users? Or maybe just the permissions of the top level folder and any sub-folder permissions are ignored?

Reasoning about hierarchical permissions like this is quite confusing and there is no default mental model people have for it.

Fair. Tbh, I would prefer tags over folders (showing my Roam stripes here :wink: ), but I imagine that would make the permissions model more complicated rather than simpler. And I get this isn't a priority. I'm sure you have a long laundry list of other items which are higher priority! :slight_smile:


I know it's not what you're asking for, but here's one way I keep my snippets organized, maybe you'll find it useful.

I set up my shortcuts to start with a specific character, based on their "affiliation". For instance:

Snippets starting with + will be Roam
Snippets starting with / are for emails

And so on.

1 Like

@Cedric_Debono_Blaze Great advice on using different starting charters for snippet triggers! We adopted the same practice early last year. We currently use the the characters /, *, -, and + to trigger shortcuts. Initially the team was intimidated at the thought if having to memorize the trigger shortcuts for such a large number of snippets. We took it a step further by being intentional about naming conventions for snippet names and their corresponding trigger shortcuts where the trigger shortcuts are logical abbreviations of the snippet name. We use a " / " for creating new cases in Salesforce, a " * " for updating already existing cases in Salesforce, and a " + " for testing and error resolving. Examples:

Case Creation: Change of Enrollment. Trigger shortcut: /coe
Case Update: Change of Enrollment. Trigger shortcut: *coe
Test & Error: Change of Enrollment. Trigger shortcut: +coe

Makes it pretty easy from there on out to keep things organized!

1 Like

Cool stuff :slight_smile: