Skip to content

Sorting and FilteringΒ #41

@clearfram3

Description

@clearfram3

What is the problem this feature would solve?

  1. Content sorting is done alphabetically at the page level. So if I want to use an llms-full.txt file, I can't just delete swathes of content that I don't need. Instead, I have to go through the whole file and look for specific pages to cut.

  2. It's not always necessary to have a whole documentation set. Being able to generate specific content sets, e.g., "A + C, but not B" would be helpful

What is the feature you are proposing to solve the problem?

  1. Section sorting: The generated content should be grouped by section, and the pages themselves should be sorted alphabetically.
  2. A configurable generator for context sets besides llms.txt and llms-full.txt.

What alternatives have you considered?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions