This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
OperStack Gates
16 quality gates for content sites, one command, free
An automatic proofreader for a whole website. One command reads every page and lists what should never go live: a title cut in the middle, a paragraph copied from another page with the numbers changed, an empty section, a link that leads nowhere, a figure with no source. Sixteen checks, thirteen seconds on 1,660 pages, and an eight-page PDF that explains each one. Free and MIT, nothing leaves your computer. It reads Markdown files: Astro, Next and MDX sites, not WordPress. npx @operstack/gates
Hi everyone. I run a pipeline that publishes to fifteen content sites, some of them past a thousand pages. Every one of these sixteen checks exists because that exact defect shipped at least once and the build log said nothing.
The one that hurt most: 121 pages sharing a closing paragraph with the numbers swapped. My duplicate checker compared exact strings, so it never saw it. Google's spam policy has a name for that pattern.
So the gates compare paragraphs with the digits masked. They also compile every MDX file up front (eleven-minute builds that fail on file 1,214 are not a workflow), check that llms.txt still matches the site, and flag any yield, occupancy or nightly-rate figure that has no source in the same paragraph.
It is free and MIT. npx @operstack/gates in any Astro or MDX project. The package ships with a fictional demo site so you can see every gate fire before you point it at your own corpus: npx @operstack/gates --demo
Happy to answer anything about the checks or the thresholds. They are all in one JSON file, and I would rather hear which ones are wrong than defend them.
One more thing for anyone whose site is not built from Markdown files: this package will not help you, but the free check on our site works on any site and installs nothing. It tells you whether assistants can read, understand and quote you: https://oper-stack.com/ai-visibi...
About OperStack Gates on Product Hunt
“16 quality gates for content sites, one command, free”
OperStack Gates was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #32 on the daily leaderboard. An automatic proofreader for a whole website. One command reads every page and lists what should never go live: a title cut in the middle, a paragraph copied from another page with the numbers changed, an empty section, a link that leads nowhere, a figure with no source. Sixteen checks, thirteen seconds on 1,660 pages, and an eight-page PDF that explains each one. Free and MIT, nothing leaves your computer. It reads Markdown files: Astro, Next and MDX sites, not WordPress. npx @operstack/gates
On the analytics side, OperStack Gates competes within Open Source, SEO, Developer Tools and GitHub — topics that collectively have 668.2k followers on Product Hunt. The dashboard above tracks how OperStack Gates performed against the three products that launched closest to it on the same day.
Who hunted OperStack Gates?
OperStack Gates was hunted by Maksim Shchegolev. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of OperStack Gates including community comment highlights and product details, visit the product overview.
Maksim Shchegolev
Hi everyone. I run a pipeline that publishes to fifteen content sites, some of them past a thousand pages. Every one of these sixteen checks exists because that exact defect shipped at least once and the build log said nothing.
The one that hurt most: 121 pages sharing a closing paragraph with the numbers swapped. My duplicate checker compared exact strings, so it never saw it. Google's spam policy has a name for that pattern.
So the gates compare paragraphs with the digits masked. They also compile every MDX file up front (eleven-minute builds that fail on file 1,214 are not a workflow), check that llms.txt still matches the site, and flag any yield, occupancy or nightly-rate figure that has no source in the same paragraph.
It is free and MIT. npx @operstack/gates in any Astro or MDX project. The package ships with a fictional demo site so you can see every gate fire before you point it at your own corpus: npx @operstack/gates --demo
Happy to answer anything about the checks or the thresholds. They are all in one JSON file, and I would rather hear which ones are wrong than defend them.
One more thing for anyone whose site is not built from Markdown files: this package will not help you, but the free check on our site works on any site and installs nothing. It tells you whether assistants can read, understand and quote you: https://oper-stack.com/ai-visibi...