A place for developers to talk about building on Farcaster.

/dev

cursor's ability to index docs is extremely powerful. while some docs sites are entirely indexable from a single entry point (foundry, gh readmes), others require more effort (wagmi @jxom)

how do we optimize documentation for indexing? seems increasingly important as we rely more and more on ai for this

1. Easily crawlable structure 
2. Turn doc site into an API to call?
3. Enable export of docs into well-formatted output via Markdown File(s) or JSON schema w/ URLs of site

you might find this firecrawl + cursor workflow helpful

🔥 🛜 🎥 Index any website and use it as context in Cursor with @firecrawl_dev 

&gt; not getting paid to say this, I just believe it's good stuff

been having issues recently with the native docs indexing built into Cursor

started using firecrawl to crawl docs sites and import… https://t.co/k8Ak0S04gX

Dan Mac

1. Easily crawlable structure 
2. Turn doc site into an API to call?
3. Enable export of docs into well-formatted output via Markdown File(s) or JSON schema w/ URLs of site

you might find this firecrawl + cursor workflow helpful

https://x.com/daniel_mac8/status/1871524305684623602?s=46&t=W5NKnRc0GRxYHUY6v-G-ZA

Save as website (full) write a parser in Python and parse the website docs into a Md. Add the Md as a knowledge base or even just keep in a documentation folder and have .cursorrules file specifically use it as a golden rule.  
 Most indexing seems to work well now, but for others I do this.

maybe vector sitemaps (newbie on subject, maybe i'm talking shit)