RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Figma] Add customizable portfolio templates

A user expressed interest in whether others prefer static portfolio templates or CMS-driven ones, indicating a desire for customizable templates in Figma for portfolios.

Original Source

@u/dvsxdev | 0 pts | 3/1/2026

For years, every time I updated my portfolio, I ended up editing code just to change content. New project? Code change. Update experience? Code change. Reorder skills? Code change. It felt wrong. So I built a small CMS specifically for developer portfolios. Main idea: * Admin panel for content * Fully customizable frontend * Built with Next.js + Payload * Structured so UI stays flexible Biggest lesson: Developers want control, but not repetitive content edits in code. I’m curious: Do you prefer static portfolio templates, or something CMS-driven? Would love honest thoughts.

Discussion

Loading comments...