𝗛𝗼𝘄 𝗜 𝗕𝘂𝗶𝗹𝘁 𝗔 𝗛𝘂𝗯 𝗙𝗼𝗿 𝗠𝘆 𝗢𝗽𝗲𝗻 𝗦𝗼𝘂𝗿𝗰𝗲 𝗧𝗼𝗼𝗹𝘀
I spent a year building the fetch-kit ecosystem.
My tools include ffetch, chaos-fetch, chaos-proxy, and the chaos arena. Each tool lives in its own GitHub repo.
I had a problem. Users visited one repo and never saw the others. They did not know how the tools worked together.
I built fetchkit.org to solve this.
Here is the stack I used:
• Eleventy v3 for fast static site generation. • Tailwind CSS v4 with a custom dark theme. • GitHub Pages for hosting. • GitHub Actions to automate builds and deployment. • Cloudflare for DNS management. • GoatCounter for privacy-friendly analytics.
Each tool has a dedicated page. These pages include code examples, comparison tables, and links to my blog posts. The homepage uses an RSS feed to show recent news.
One technical tip for your setup:
If you use GitHub Pages with a custom domain and Cloudflare, keep your A records as DNS only. Do not turn on the Cloudflare proxy for these records.
GitHub checks if your domain points to its own IPs. If Cloudflare proxies the traffic, GitHub sees Cloudflare IPs instead. This causes GitHub to mark your domain as misconfigured. This stops your site from serving. You can proxy the www CNAME record without issues.
You can view the site source here: github.com/fetch-kit/fetch-kit.github.io