Launch revamp: rebrand to P2Pool Starter Stack, v1.0 copy, FAQ + SEO/GEO#2
Merged
Conversation
Drop the "Hardrock" name across the site in favor of the org name, P2Pool Starter Stack, and update the landing copy to match where the two projects actually are now. Brand: - Rename Hardrock → P2Pool Starter Stack everywhere (title, brand, meta description, header/footer wordmark, copyright, README, source comments). - New layered "stack" mark replacing the crystal, in the icon set and favicon; responsive wordmark sizing so the longer name fits the header on mobile. Content (matches current repo state): - Roadmap: v1.0 is feature-complete. RigForge's v1.0 is fully closed and Pithead is through its E2E release gate, so the waves now read Shipped (correctness, privacy/security, dashboard, CI/tests) with only the release pipeline + launch assets left. Operator alerting moved to the v1.1 card. - RigForge: add the measured benchmark (+3.5% hashrate / +7.6% efficiency on a 7800X3D, +6.6% on a 48-core EPYC), macOS support, commit-pinned stock XMRig, and a "verified, idempotent" feature. - Pithead: sharpen features to the README (donate-minimum optimizer, honest tier + VIP status, scoped Docker-socket proxies). Verified: strict Hugo build (--panicOnWarning) and htmltest both pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ess documented) Match the org profile README: "Tor-only upstreams" overstated v1.0 — inbound rides hidden services, but a couple of outbound yield paths still touch clearnet until the Tor-by-default flips in v1.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Launch-readiness polish on the showcase site: - Add a branded 1200x630 og:image / twitter:image so shared links render a preview card (head.html previously set twitter:card but no image). Source SVG in assets/og/, rasterized to static/img/og-card.png via rsvg-convert. - RigForge: link docs/benchmarks.md so the measured +3.5%/+7.6% figures point at their methodology, and surface the 0% dev fee (XMRig's donate-level pinned to 0) — a trust point the XMR audience looks for. Strict Hugo build + htmltest pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
VijitSingh97
changed the title
Layers on top of the v1.0 rebrand so the site is surfaced — and cited — when people (or their AI assistants) ask how to mine Monero privately. No design changes; the visual system and existing copy are untouched. - FAQ section (data/content.yaml → faq, rendered in index.html with native card styling). Nine real questions: how to mine Monero at home, ports/IP, P2Pool vs centralized pools, solo vs pool, hardware, merge mining, fees, reusing existing rigs, XvB. Persuasive and keyword-rich, doubles as objection handling for the Reddit/X audience. - JSON-LD structured data (layouts/partials/schema.html): Organization, WebSite, a SoftwareApplication for Pithead and RigForge (free, MIT, OS-tagged), and a FAQPage generated from the same faq data so visible copy and schema never drift. Emitted via jsonify | safeJS; validates as JSON. - head.html: keywords, author, robots max-image-preview:large, og:locale, twitter:title/description/image:alt, theme-color, and the schema partial. - robots.txt: explicitly welcomes answer-engine crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, …) alongside the sitemap. Also flips enableRobotsTXT off in hugo.toml — Hugo's generator was clobbering the hand-written static/robots.txt with a bare "User-agent: *" (so the custom rules and even the existing Sitemap line never actually deployed). - header: FAQ nav link. - README: documents the discoverability layer. Verified: hugo --gc --minify --panicOnWarning clean; htmltest passes; JSON-LD parses with 9 FAQ entries; deployed robots.txt carries the AI-crawler rules + sitemap; sitemap.xml still generated; FAQ grid renders on-brand. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
VijitSingh97
force-pushed
the
claude/fervent-gould-d16af7
branch
from
1991a71 to
d74284a
Compare
pithead 1.0.2 ships an installable release bundle, so the documented install is now "download the latest pithead.tar.gz → copy the config template → setup" rather than git clone (which is now the build-from-source / dev path). Update the hero terminal to match the README's Quick Start so the site stays consistent with the shipped project. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a version badge to the Pithead and RigForge cards (e.g. v1.0.2 / v1.0.1), linking to that repo's releases/latest. Done without breaking the site's "zero third-party requests" promise or the network-free CI: - data/releases.json — committed fallback tags the Hugo build reads locally; the build never calls out, so CI stays deterministic under --panicOnWarning. - scripts/refresh-releases.py — best-effort updater that pulls the latest tags from the GitHub Releases API (keeps the fallback on any error; honors GH_TOKEN to avoid the rate limit). - deploy.yml — runs the refresh before each Hugo build (with the built-in GITHUB_TOKEN) and on a daily schedule, so the live badges track new releases without a manual push. - Version chip styled per-card accent (orange / ember); header wraps on mobile so the chip + ★ flag never overflow. Verified: hugo --gc --minify --panicOnWarning clean; htmltest passes; chips render v1.0.2 / v1.0.1 with correct links; refresh script runs locally. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Revamps the landing page to match the current state of pithead and rigforge, drops the Hardrock name for the org name P2Pool Starter Stack, and gets the page launch-ready for Reddit / X — and built so AI assistants and Google surface it when people ask how to mine Monero privately.
Companion PR (consistent copy): .github#1.
Rebrand (Hardrock → P2Pool Starter Stack)
favicon.svg.Content refresh — matches where the projects actually are
Launch readiness — SEO / GEO + FAQ (new)
Layered on top of the rebrand, no design changes:
layouts/partials/schema.html) — oneapplication/ld+jsongraph:Organization,WebSite, aSoftwareApplicationfor each of Pithead and RigForge (free, MIT, OS-tagged), and aFAQPagegenerated from the same FAQ data the page renders, so visible copy and structured data never drift. Built viajsonify | safeJS; validates as JSON.robots: max-image-preview:large,og:locale, Twitter title/description/image:alt, theme-color.sitemap.xml.Verification
hugo --gc --minify --panicOnWarning— clean, zero warnings/deprecations.htmltest— passed (internal links + in-page anchors, incl. the new#faq).🤖 Generated with Claude Code
Dynamic version badges (added)
Each project card now shows its latest release tag (v1.0.2 / v1.0.1), linked to
releases/latest. To keep the site's zero third-party requests promise, the version is baked in at build time from a committeddata/releases.json; the deploy workflow refreshes it from the GitHub API before each build (and on a daily cron), so badges track new releases without a push. CI stays network-free and deterministic.