Query to format structured blocks into table

Questions & Help Queries
4
  • All the real-life examples that you shared so far are better served by properties.
  • Regarding your concerns:
    • Nested blocks are not as naturally related to tables as it seems on first sight.
      • Nested sibling blocks don’t enforce any particular structure without a template.
        • They can get easily messed up when:
          • the order is modified
          • a block is missing
        • Changes to Logseq templates currently don’t update existing blocks.
          • When this problem appears, it can be too late.
      • A table can be expressed as a nested structure in two ways:
        • rows of cells: this is the typical way, used e.g. in HTML
        • columns of cells: this is your way and seems less natural
      • Though useful, tables are not very natural themselves to begin with.
      • A block holding a single value is kind of a waste.
    • In contrast, a property-oriented template doesn’t create children, but properties within a single block.
      • For some ideas, have a look at Can LogSeq glossaries and abbreviation directories
      • For a more natural way of entering information, consider using Inline properties
      • As a graph gets bigger, filtering becomes increasingly important.
        • Given that a query will be used anyway, properties provide many filtering options that nested blocks cannot.
1 Like