Logseq/Pref/Page/Name

• Page name preferences

  • This encode garden prefers singular canonical page titles and Title Case namespace segments where English prose allows.
  • Multi-word concepts use nested paths (Parent/Child/...) rather than kebab-combining a phrase into one segment when a type or topic warrants hierarchy—for entity type documentation see Logseq/Entity (for example Logseq/Entity/Software/Project).
  • Plural, shortened, or contextual link surfaces belong in alias:: per Logseq/Frontmatter/alias; do not encode parent context twice in alias:: when the title already carries it.
  • Creator namespace with type segment: when a work's creator already has a namespace in the garden, place the entity under Creator/Type/Short Name — interpose a type segment (e.g. Font, Book) between the creator and the leaf, matching the pattern of Person/Douglas Hofstadter/Book/85/Metamagical Themas. Drop redundant creator and type words from the leaf: JetBrains/Font/Mono Nerd, not JetBrains/JetBrains Mono Nerd Font. Reserve type-only top-level namespaces (e.g. Font/<Name>) as a fallback when no creator namespace exists. Exception: entities well-known enough to warrant a top-level page (e.g. Lazygit, tmux) may stay at the top level regardless of creator.