# Meta-Naming All files and folders in this vault follow a harmonized naming pattern and or style, depending on their use-case. ## Conventions - Filenames must only contain ` `, `[A-Z]`, `[a-z]`, `-`, `_` or `[0-9]` - except for the extension - Special characters in external names (e.g. brands) will be replaced (e.g. a `|` in the name of a bot becomes ` - `) ## Prefixed files Some note types are prefixed by ab ID or name, to make then visually stand out wherever they are queried and also easier to process by plugins etc. - **Fieldnotes** are prefixed by the letter `f` and a alphanumeric ID: `f1a1...`. The order of letters and numbers shows the order of the "train of thought" and indicates how a series of connected notes emerged - **Zettels** are prefixed by the letter `z` and a alphanumeric ID: `z1a1...`. The order of letters and numbers shows the order of the "train of thought" and indicates how a series of connected notes emerged. The ID of a Zettel never changes - **Templates** are prefixed by the letter `t` and an alphanumeric ID: `t1a1...`. The order of numbers and letters shows the relation of the templates to each other. Template ID's can be changed to reorder them - If a notes closely relates to a reoccurring group, like documentation of software-specific plugins or configuration, it is prefixed by the name of the software (e.g. "Obsidian-Iconic" for documentation how the plugin iconic for Obsidian is used). This is mostly used for meta-files, as most of the notes are created as Fieldnotes - **SOPs** are prefixed by the letter `s` and an alphanumeric ID: `s1a1...`. The order of numbers and letters shows the relation of the SOPs to each other. SOP ID's can be changed to reorder them ## Non-prefixed files A number of files do not have a prefix, these sit "between" grouped files and the main notes. Most notably, these are index-notes for note-types, entities and note-categories, serving as a central hub. These only consist of a single word in the name (e.g. *Software*, *Companies* or *SOP*). ## Temporary files Files that only have a short half-life (like fleeting notes) follow a naming pattern that is visual distinct from all other notes and is **based on its date and time of creation**. `YYYY-MM-DDTHHMMSS` ## Helpers All files considered to be "helpers" for maintaining the vault itself are **written in lower-case**. These are: - [[Meta-Templates|Templates]] - [[Meta-Bases|Bases]] ## Logs Logs always contain a **reference to their creation date** in the filename. These use [MomentJS](https://momentjs.com/docs/#/displaying/format/) formatting. - **Daily:** `YYYY-MM-DD` - **Weekly:** `gggg-[W]ww` - **Monthly:** `YYYY-MM` - **Quarterly:** `YYYY-[Q]Q` - **Yearly:** `YYYY` - **Project log:** `YYYY-MM-DD_Project_Log` An exception are TTRPG-session logs, as these are ordered by an interated session number at the end of the filename (`..S01, ..S02 and so on`). ## Special files Some files are needed for non-standard configurations. These include: - `*.css` files to apply style-overrides to the vaults theme or the published format of the vault. These are either named in a format required format of a plugin (e.g. `publish.css`) or in lowercase indicating its purpose (e.g. `override-sidebar.css`) --- ## Related - **previous** [[Meta]] - **see** [[Meta-Notes]] for available notes types - **see** [[Meta-Templates]] for available templates - **see** [[Meta-Bases]] for available bases ## Sources - **references** [MomentJS](https://momentjs.com/docs/#/displaying/format/) for the time-based formatting ## Usage - **used in** none --- ## Changelog - [[2026-06-07]]: Initial creation