Logseq/Entity/Person

• Person

  • In this garden, Person pages model real individuals tracked as first-class hub pages under Person/Full Name.

  • Namespace vs entity type

    • A hierarchical title under Person/ does not imply every child page is a person entity. Example: Person/Someone/GitHub/dotfiles is usually a Logseq/Entity/Software/Project instance (or another type), nested for organization and SCM style—not a second “person” instance. Choose logseq-entity:: from content and role, not from the Person___ filename prefix alone.

  • What counts as a person entity (instance)

    • Person hub pages only: disk file Person___<Name>.md where <Name> contains no ___ (Logseq title is Person/<Name> — two path segments). Examples: Person___Drew DeVault.md, Person___Jan-Erik Rediger.md.
    • Not person entities: deeper paths such as Person___Foo___GitHub___bar.md, Person___Foo___Blog___..., or other child pages—model those with the appropriate type, often Logseq/Entity/Software/Project for GitHub project pages.

  • When to create a person page

    • Strong signals: individual is a maintainer, author, speaker, or public figure likely to be linked repeatedly; confirmed identity; useful to attach bios, handles, and project subpages.
    • Prefer site-specific namespaces for low-signal identities such as forum users or one-off commenters.

  • Naming and links

    • Default page: Person/Full Name — disk Person___Full Name.md.
    • When linking in prose or new notes, use the page's real title (the filename / Logseq title), not convenience aliases.
    • Do not introduce People/... as a page title, alias, or “plural reference” pattern. This garden does not use a parallel People/ namespace for persons.
    • Optional alias:: is only for real alternates: prior title after a rename, spelling variants, handles, or other non-People/ contextual links—same spirit as company alternate names—added only when codekiln asks for them, per My/AI/Rule/Logseq/No Aliases Unless Asked.

  • Finding and deduplicating

    • Search in order: exact Person___*.md title; alias:: match; partial name / handle in pages/Person___*.md; body text (bio, same GitHub profile URL). Classify: existing, similar, new, or blocked.
    • One page per person. Never split the same human across two hub pages; merge or pick one title.

  • SCM projects under a person

    • Repos under a person use Person/<Name>/GitHub/<Project> when the maintainer is clear and the person hub exists or should exist. Those project pages are Logseq/Entity/Software/Project entities, not person entities.

  • Frontmatter on person hub pages

    • Mark the hub with logseq-entity:: [[Logseq/Entity/Person]], or with its maker entities alone when Logseq/Entity/Person/Maker applies.
    • Shared frontmatter conventions live on Logseq/Frontmatter.

  • Page shape

    • LFM; first content block is typically - # … with the person’s name; lean sections (About, Online presence, Projects) and links to child pages as needed.

  • Related types

    • Logseq/Entity/Person/Professor — a person with a verified professorial appointment. Professor hubs retain the Person/Full Name title and carry the more specific Professor entity alone in that lineage.
    • Logseq/Entity/Person/Knowledge Gardener — applied alongside this type when the person keeps a public digital garden.
    • Logseq/Entity/Person/Maker — a person who makes music, music theory, music technology or art, such as a Composer or a Sound Artist. A maker's hub lists only its maker entities in logseq-entity::, so this page's linked references leave makers out. The hierarchy on Person lists every Person/<Name> hub, makers included.
    • Logseq/Entity/Person/Character — fictional characters, not real-person hubs.