Skip to content

Support tabular embedded nodes #26

Closed

Description

@mindsocket

Related to #5

We currently support embedded entities by way of headings or bullet points. It would be useful to be able to enumerate a set of solutions, risks, assumptions, decisions, etc. In the form of a table instead of being forced to use a bulleted list. This would involve extending the current markdown parsing to parse tables and extract from those tables a set of node entries with props based on the the column headings (eg title, status, ...).

We'll need to come up with a good way to determine the node type as that should be expressed once. we might need to try and detect a heading that's annotated with a type as we do already but then detect when there's only a table under that heading, signalling a list of entities of that type (in that case the heading content is otherwise ignored, it's not a title). Heading to know what type the table rows represent

Activity

  1. mindsocket commented on Mar 9, 2026

    @mindsocket
    OwnerAuthor

    Regarding tabular parsing - we could look in the first cell of the header row as a way of inferring node type, or base this on a natural language heading that follows the hierarchy level pattern (depending on implementation of #27). This would allow automatic type detection while maintaining flexibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions