Logseq/Entity/Concept
Concept
- In this garden, Concept pages model understanding-oriented topics that follow the garden’s Diataxis-style shape (aligned with Diataxis/Concept / Diataxis/Explanation): paradigms, architectural lenses, and other “big ideas” explained rather than only defined.
Examples in this garden
When we treat something as a concept entity
- Strong signals: the page’s purpose is understanding—what something is, why it matters, how it relates to neighboring ideas—not primarily a how-to, tutorial walkthrough, or lookup reference.
- Good fit: programming paradigms, frameworks of thought, architectural patterns explained in prose.
Naming and links
Finding and deduplicating
- Search for an existing page before creating a new concept entity.
- Search order hints: exact title, alternate titles from frontmatter, normalized topic phrases, sibling pages in the same topic area.
- Classify as: existing, similar (needs human judgment), new, or blocked.
Frontmatter
- On instances, set
logseq-entity:: to a link to this entity-type page so backlinks list all concept entities. - Concept-specific tags may mirror the established Diataxis concept cluster when the page is new and that convention applies.
- Shared frontmatter conventions live on Logseq/Frontmatter.
Page shape (body)
- Use Logseq Flavored Markdown (bullets, headings as bullets, tab nesting, no blank lines between bullets).
- Recommended sections (Diataxis explanation style): Overview, Context, Key Principles, Mechanism, Examples, Misconceptions. Adapt headings to the topic; not every section must be long.
- First heading after frontmatter: H1 matching the page’s primary topic.
Combined with other types
Relationship to Diataxis