Bug reports, content suggestions, and ideas for search.corrode.dev, the community-curated search engine for the Rust ecosystem.
search.corrode.dev is a focused search engine for high-quality Rust content: blog posts, conference talks, podcast episodes, research papers, and more. It is built and maintained by corrode.
This repository is the public feedback tracker for the search engine. The code that powers the site is currently a private repository, but the experience belongs to the community, so the conversation about it should be public.
Use this repo to:
- Report bugs: something broken in the UI, a result that should not be there, broken pagination, weird ranking.
- Suggest content: a blog, podcast, conference, or paper source that should be indexed.
- Request features: filters, integrations, a better mobile experience, an API endpoint you would like to see.
- Start a discussion: share how you use the search, propose ranking changes, ask questions, or just say hi.
A few things that make reports much easier to act on:
- Include the query. A screenshot is great, but a copy-pasteable query (or the full URL with parameters) is better, since it lets us reproduce the exact ranking you saw.
- Tell us what you expected. "I searched for X and expected Y near the top, but got Z" is gold.
- For missing content, include the canonical URL (RSS feed, sitemap, or author page) so we can wire it into the crawler.
- For UI bugs, mention your browser and whether you are on desktop or mobile.
The issue templates will walk you through the right fields.
Use issues for:
- Something is clearly broken.
- A specific result is wrong.
- A source is missing.
- A concrete feature request.
Use discussions for:
- "Would it make sense if ...?"
- Ranking philosophy and trade-offs.
- General questions about the project.
- Show and tell, use cases, integrations.
Not sure which? Open a discussion. We can convert it to an issue if it turns out to be a bug.
The search engine itself lives in a separate repo that is not open source (yet). This feedback repo does not accept pull requests. Please open an issue or a discussion instead. We are much more interested in what should change than in code changes here.
If you want to contribute on the content side, the best way is to suggest sources via the content suggestion template.
This is a corrode-run space and follows the spirit of the Rust Code of Conduct. Be kind, be specific, and assume good faith. The search is a labour of love and feedback is genuinely appreciated.
- Search: https://search.corrode.dev
- corrode: https://corrode.dev
- Rust newsletter: https://corrode.dev/blog
- Idiomatic Rust resources: https://corrode.dev/blog/idiomatic-rust-resources/
Made with care by corrode.