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.

RequestHunt

Loading request...

Develop a robust and maintained .NET Static Site Generator | RequestHunt

Develop a robust and maintained .NET Static Site Generator

| | , , ,

by @Justin Yoo | 1/3/2026 | submitted by AutoCollector

[view original source]

Users express a long-standing desire for a well-supported static site generator built on the .NET platform, citing past attempts and the lack of a current, viable option compared to other ecosystems. They wish for a solution that is actively maintained and easy to use.

Original Source

@Justin Yoo | 70 pts

How come there's no static site generator in .NET? Around 11 years ago, I started this idea when .NET Core 1.0 was released as RC1. The initial idea was very simple. With RazorEngine, razor templates were easily converted to HTML files. Therefore, as long as I write razor templates as a theme and convert markdown to HTML, it seemed to be doable. As a result, an alpha version was released, but it was soon forgotten because I wasn't able to manage my spare time for this. 6 years later, Blazor came out to the world. It was much easier to use for building a web app. My abandoned idea started talking to me, "It's time to revive!". So, migrated the old codebase to Blazor. But again, it was piled back into my backlog while migrating the old codebase. At the end of 2025, while I was taking holidays with family, it came to me and whispered, "You can do it this time with AI, can't you?". That's right! I opened my VS Code and started asking my GitHub Copilot for idea whether it's doable or not. GitHub Copilot showed me some code snippets how to convert razor template with markdown files to HTML documents without having to run a Blazor server. Not to surprise, the code GitHub Copilot showed me was dead simple! So, I started coding to implement my idea to actual product, ScissorHandsNET! https://lnkd.in/ghsmpz5f It's a static site generator, based on Blazor, and collaborated with GitHub Copilot. It's extremely flexible and extensible through plugins, and customisable through themes. It's completely open-source under the MIT license. So, if you've ever been looking for a .NET-based static site generator, it's yours. I haven't started migrating my personal blog sites using this ScissorHandsNET yet, but it will be happening sooner rather than later. Curious of ScissorHandsNET? Go get the code and try it by yourself, and let me know your thoughts! https://lnkd.in/ghsmpz5f #dotnet #blazor #staticsitegenerator #ssg #github #copilot #githubcopilot #getscissorhands #scissorhandsnet

Discussion

Loading comments...