Logseq/Entity/Book/Section
Book Section
- In this garden, Book Section pages model one headed part of a book or manual as a navigable Logseq page.
What counts
Identity and names
- A section is identified by its source work and its place in the heading tree. Search the intended path, aliases, and existing section content before creating a page; a changed heading or shortened title does not make a second section.
- Nest each section under its parent page. Prefix each segment with a two-digit sibling order from the source, followed by a short, recognizable heading. Shorten long heading words where the meaning stays clear. The full source heading belongs in the page's H1, with its source number where useful.
- Number siblings in source order, including unnumbered headings that qualify as sections. Keep the number local to the parent:
06 Dig Osc/02 Param Controls, then 02 Param Controls/01 Knob Speed.
Page shape
- Use the level-specific
logseq-entity:: marker. up:: links to the parent page; prev:: and next:: link to adjacent siblings when those pages exist. The first and last sibling need only the available direction. See Logseq/Frontmatter for shared frontmatter conventions. - Begin with one bullet-wrapped H1. Put the section's own content under it in source order. Embed each imported child page once at the point where its heading occurs. The child page holds the text; the parent does not repeat it.
Only embed L1 -> L2 -> L3
- The Logseq user interface becomes messy-looking and sluggish when more than two levels of pages are embedded and are visible on a single page. It's okay if page MyPage has
{{embed [[MyPage/MySubPage]]}}, and if MySubPage has {{embed [[MyPage/MySubPage/MySubSubPage]]}}, in it. It could be okay if there's only a single embed goes deeper and it's a very small page. But if the nesting goes deeper than that, it's usually a poor experience for the page viewer. As a convention, we permit embeds of L2 in L1 and L3 in L2, and use typical logseq wikilinks to L4. - Example/Good
Use Block References deeper than Level 4
- If a page has a section like 1.2.3.4.5, then 5 should be a heading on the level 4 page. If another page references 1.2.3.4.5, then a Logseq/Block/Id
- A newly available child appears in its parent's embed list, and adjacent sibling pages link in both directions through
prev:: and next:: once both exist. - Turn the source's paragraphs, bullets, callouts, figures, and tables into readable nested blocks. Preserve the information needed to use the material, not the PDF's line wrapping or table grid. Use
> [[Note/Info]] or > [[Note/Warning]] for corresponding callouts. - Place a figure under its caption block. Represent the image with a Logseq/Entity/Asset/B2 page beneath its owning section; Logseq/Entity/Asset defines its page-derived filename. Embed the verified remote URL with the caption as alt text. Keep the full PDF outside the graph.
- Replace page-number references with a link to the corresponding section when it exists and its identity is clear. Otherwise, name the destination in prose without a speculative link. Do not preserve a bare PDF page number as navigation.
Source check
- Compare the extracted text and images against the source pages: heading order, callout scope, figure/caption pairing, and cross-references can be lost in PDF extraction. The imported page should read naturally in Logseq and nvim.
Example