funnel: converting GitHub Pages landing page (docs/index.html) for all 33 tools#3
Open
deemwario wants to merge 1 commit into
Open
funnel: converting GitHub Pages landing page (docs/index.html) for all 33 tools#3deemwario wants to merge 1 commit into
deemwario wants to merge 1 commit into
Conversation
The repo had no landing page — only the README. This adds a single-file, dependency-free GitHub-Pages landing for all 33 tools, grouped by the README's 9 categories, with the OSS->deemwar.com/contact funnel. - House style ported from the existing design; one card per tool (code link + the README's story link), hero + install snippet + 3x deemwar.com/contact CTAs. - Honest by construction: no fabricated metrics — stats are '33 tools / 0 deps / 1 script each / heuristic & honestly labelled', matching the README. - Self-contained (inline CSS, no JS/CDN, no build). Render-verified locally. Note: enabling GitHub Pages to SERVE this is the owner's deploy tap — this PR only stages the file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Funnel: converting GitHub Pages landing page (docs/index.html)
#ossengine cycle 6 —
READMEs/funnel, no owner gate for the file itself (enabling Pages to serve it is the owner's deploy tap). Independent of PRs #1/#2.Why
The repo's only funnel surface was the README. This adds a shareable, converting landing page — a cleaner top-of-funnel for Show-HN/social than a GitHub README.
What's in here (1 file + .gitignore)
docs/index.html— single, dependency-free GitHub-Pages landing for all 33 tools, grouped by the README's 9 categories (incl. the "Lint every channel" section with the 4 channel-lint tools). One card per tool: code link + the README's exact story link. Hero, install snippet (git clone …/deemwar-products/agent-ops), and 3×deemwar.com/contactCTAs.Verification
Render-verified locally (served over HTTP, screenshotted): house style intact, hero + 33-tool grid + CTA all correct, 0
muthuisherereferences, all URLs →github.com/deemwar-products/agent-ops.Owner tap
This PR only stages the file. Enabling GitHub Pages (Settings → Pages →
docs/) to actually serve it is the owner's deploy decision — outward-facing, kept gated.🤖 Generated with Claude Code