Skip to content

Support natural language headers for embedded nodes #27

Closed

Description

@mindsocket

This needs more thinking through.

Currently we support bulleted lists annotated with type anchors or inline properties. This can get a bit verbose. Instead we could support a heading that matches a no type and then treat all bulleted points underneath that as being of that type. Example below...

... Existing page content, up to mission level

### Goals
- A goal - we know this is a goal because the heading above matches a node type (singular, lower case: goal)
- Another goal

It's not yet clear yet that this is going to be helpful, so let's park this idea for now

Activity

  1. mindsocket commented on Mar 9, 2026

    @mindsocket
    OwnerAuthor

    For natural language support, we could add natural language terms to HierarchyLevel (design TBD - could be a plural field, or a synonyms field, or similar) for the purposes of supporting this idea. This would make the system more flexible in recognizing various forms of headings while maintaining a canonical type system.

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