Templates and Snippets let you reuse the structures that work without giving up the simplicity and portability of ordinary OPML files. Templates create complete new outlines; Snippets add reusable branches to an outline you are already editing.
Both features are included with Traverse Pro.
Set up the special folders
Create one or both of the following folders at the top level of your active Traverse library:
_templates_snippets
The names must include the leading underscore and use lowercase letters exactly as shown.
Template OPML files can be placed directly inside _templates or organised into nested folders beneath it. Traverse mirrors that folder structure in the Templates menu. Snippet collection files should be placed directly inside _snippets.
They are regular outline files
A template or snippet source is a normal Traverse OPML outline. You can open and edit it like any other outline, use hierarchy, and include supporting notes, checkboxes, types, marks, and custom attributes.
The outline title is used to identify the source in Traverse's menus. Because the source remains an ordinary OPML file, it can be copied, backed up, shared, or edited with compatible tools.
Using Templates
Place each reusable starting outline in _templates or one of its nested folders. Once Traverse finds at least one template, the New Outline menu offers a choice between a blank outline and your available templates.
Creating from a template makes a new, independent outline in the library folder you have selected. Traverse copies the template's complete structure, text, notes, attributes, numbering settings, default view, and other document metadata, while giving the new outline its own document and node identities.
A template's default view takes precedence over the general default for new blank outlines. Set it in the template's Document Details when you want, for example, a screenplay template to open in Writer view or a planning template to open in Column Manual.
Later changes to the template affect outlines created from it in future; they do not rewrite outlines that have already been created.
Using Snippets
Place snippet collections directly inside _snippets. Each OPML file becomes a named collection in the Add Snippet menu, and each top-level node in that file becomes a snippet choice.
To insert a snippet, select the node that should become its parent, then choose Add Snippet from the context menu, toolbar, or app menu. Traverse inserts the chosen snippet node's children beneath the selected node. Their nested structure, text, notes, task state, and attribute values come with them.
Use the top-level nodes in a snippet file as menu labels and place the content you want inserted beneath them. For example, a top-level node named New Book might contain child nodes for bibliographic details, reading notes, quotations, reflections, and questions.
How snippet attributes are merged
When a snippet uses custom attributes that are not yet defined in the target outline, Traverse adds those definitions automatically. Existing definitions with the same key are reused rather than duplicated, and lookup choices from the snippet and target outline are combined.
Attribute dividers from the snippet source are not added to the target outline. This keeps the target document's Inspector layout intact while still bringing across the fields needed by the inserted nodes.
Useful ways to work
- Use nested Template folders to group repeatable structures by client, project type, writing format, or area of work.
- Use Templates for whole-document structures such as project plans, meeting systems, research maps, book notes, and writing frameworks.
- Use Snippets for smaller branches such as a task checklist, review questions, decision record, source note, or status workflow.
- Give template roots and snippet choices short, descriptive titles so their menus remain easy to scan.
- Keep source files deliberately generic. Add the structure and prompts you want to reuse, then customise each new instance.
