-
Notifications
You must be signed in to change notification settings - Fork 32
Description
Prerequisites
- I have searched existing issues to ensure this feature hasn't already been requested
- I have tested using the latest version of docs-builder
What problem are you trying to solve?
I think it would be useful for the assembler index command to also provide the option to index the source of our documents, and not only the build.
When doc writers work we always work with the source of the docs, of course thinking of the final outcome but analyzing the source and working with snippets, admonitions, tabs, etc.
When using Cursor or another AI assistant, the context that we provide to the assistant is basically the source, and not the final build, and we ask for help or analyze the source more than the final build.
Because of that it could be useful to index the source also into Elasticsearch for RAG purposes, or for any other type of analysis.
Anyway I consider this secondary (because we already have Cursor and the AI Assistants to work locally with our sources), the most important part is what you have already covered in an awesome way with assembler index :)
PS - use case example
Analyze the docs to find improvement and optimization areas to convert to snippets: if we index the build, the AI assistant is not able to determine if the content of the docs comes from a reused snippet or it's actually duplicate.
Proposed Solution
Add a flag or a new command to index the source, allowing to filter and deciding what sources to include or exclude.
Examples and Research
No response
Alternative Solutions
No response
Additional Context
No response
How important is this feature to you?
Nice to have