Folder notes

For every folder foo/ in your notebook, if a exists alongside it, it is consider a “folder note” that is associated with the folder. Likewise, an associated foo.yaml servers as the YAML configuration for the entire folder and its contents recursively.

The children of folder notes become its folgezettel children by default.

Instead of, you can also use foo/ (or if using Org Mode ✍️) or foo/index.yaml. Internally, Emanote will treat them as and foo.yaml respectively.

Links to this page
  • YAML configuration

    Configure your site metadata, rendering configuration and such using YAML configuration. Create a foo.yaml alongside (see Folder notes) or foo/ folder, and those settings apply only to that route. The YAML structure is the same as your Markdown frontmatter, and vice-versa. Settings in the YAML frontmatter apply onto that Markdown route only; whereas settings in an individual .yaml file apply to that entire sub-route tree. Emanote does a deep-merge of the parent YAML configurations, so you can have children override only what’s necessary. This is sometimes known as “data cascade”. The final merged YAML structure is passed to the HTML templates, of which you have full rendering control over.

  • Sidebar
    if template.sidebar.folders-first is set to true (default false), directories (see Folder notes) are put before single notes, respecting the other order criteria. Otherwise, directories and notes will be interleaved.
  • Folgezettel links

    By default, Emanote includes any directories in your note’s path as vertices in the folgezettel graph. This makes the folder note a folgezettel parent of the child note. The contents of a folder, likewise, become folgezetten children of the folder note. For eg., in foo/bar/, “foo” is a folgezettel parent of “bar”, and “bar” is a folgezettel parent of “qux”.

    [!tip] Put this configuration in if you want to disable folder folgezettel for just that folder note foo/. Put it in foo.yaml if you want to disable it for foo/ and all subfolders under it recursively. Put it in top-level index.yaml to disable it for all folders. See YAML configuration for more details.