Extend the power of @docs feature through adding a list of pages manually to a docs, or support for documentations created by gitbook, etc

Hi everyone, thank you all for creating this incredible tool and making it available at a reasonable price based on usage and use cases. :heart:

As a web3 security researcher, I need to analyze different projects’ codebases and their documentations to gain insights into how they function. Many of these documents are created using GitBook and then customized afterward. Alternatively, the documentation pages are nested, making it challenging to find all the links on a single page. Furthermore, the links and data fetching are specifically designed in a way that the cursor’s docs feature cannot locate any links from the project’s documentation page. At best, it can find only a few of them.

It would be a fantastic addition if you could include a feature to edit the documentation in the Cursor. This would allow us to append a list of URLs to it. We could then use our own crawlers to extract all the pages’ links from the documentation and add them to the incomplete documentation items in the Cursor.

Additionally, it would be amazing if the Cursor’s crawler could be enhanced to fetch all pages from documentation created using GitBook. GitBook is a highly convenient documentation structure for web3 projects.

Another way to improve the Cursor would be to save the documents in a JSON format somewhere, allowing users to edit and add more content. This way, users can create their own customized documents from various sources for complex projects that require different documentations from different sources simultaneously.

I’m not sure which approach you prefer or which is more convenient to implement, but I hope you all can do the best you can. :100: