What Mechanical Keyboard Ideas Weekly Actually Is
It is a weekly roundup that curates interesting mechanical keyboard projects, custom builds, and design ideas from across the enthusiast community. Most weeks you get a digest of about 15 to 25 linked projects spanning everything from full-size ergonomic boards to split ortholinear builds and unusual form factors. The value is mostly in the curation. You spend your time scrolling through GitHub repos, Reddit threads, and personal blogs that you would otherwise never find without a dedicated search. I subscribed to it about three years ago when I was looking for alternatives to my existing setup. The first few weeks I found enough inspiration to redesign my entire home office input device list. That said, it is not a tutorial site. The posts are summaries with links to the original creators. You go there if you want build logs, files, or detailed guides.
How Mechanical Keyboard Ideas Weekly Saves You Time
The main use case is research. If you are planning a new build and need visual reference or want to see what layout combinations other people have actually shipped, this gives you a starting point without spending six hours digging through r/MechanicalKeyboards or Keyboards forums. A typical session where I browse the weekly issue takes about twelve minutes. I usually bookmark two or three projects that look worth investigating further, then spend another thirty minutes to an hour reading the linked documentation. I once used it to find a community member who had designed a split columnar board with an integrated trackpad and palm rest. The original post linked to a GitHub repository with KiCad files and a step file for the case. I ended up 3D printing a modified version for my own hand size. The process from discovery to first print was roughly three weeks including learning the routing software and troubleshooting the case tolerances.
Where to Find It
The weekly digest is hosted on the Mechanical Keyboard Ideas Weekly website and is also distributed through their newsletter. You can subscribe using an email address and you will receive a formatted HTML email each week with thumbnails, brief descriptions, and direct links. They also maintain an archive page where past issues are searchable by tags like split, ergonomic, low profile, and macro pad. There is no paid tier. The site runs on ad revenue and occasional community donations. If you prefer RSS, they offer an Atom feed. I use the feed because the email sometimes gets pushed into my spam folder depending on the provider, which I found out the hard way during a particularly busy month when I missed two consecutive weeks.
Get the Full Details
Common Pitfalls When Using This Resource
Beginners often treat the weekly as a shopping list instead of a research starting point. A lot of the projects linked are one-off builds with incomplete documentation. Some require proprietary firmware or custom PCBs that are no longer in production. I learned this the hard way when I spent an entire Saturday trying to flash firmware for a board that had been abandoned by its author and moved to a different controller platform. The workaround was to check the linked author profile and GitHub commit history before committing to any build. If the last commit is older than eighteen months, you are mostly on your own for support. Another issue is copycat culture. Several of the projects in recent issues have been nearly identical clones of earlier designs with minor case color changes. The curation team does flag original versus derivative work in most cases, but not consistently. Cross-referencing with the comments section on the original posts usually reveals whether a project has been reused without credit.
Who Should Use This and Who Should Not
If you are new to mechanical keyboards and just want a plug-and-play solution, this is not the right resource. You will encounter a lot of projects that require soldering, firmware configuration, and CAD modification. The learning curve is steep if you have never opened a keyboard before. On the other hand, if you already know how to flash QMK or ZMK and have access to a basic soldering station, the weekly digest can accelerate your research significantly. I would estimate it cuts down the initial ideation phase from about four hours of random browsing to roughly twenty minutes of targeted scanning. There are downsides to relying on any single curated source. The selection skews toward wireless split and ergonomic boards because those are the projects enthusiasts are most excited to share. You will find fewer posts about budget builds under fifty dollars, vintage conversions, or industrial-grade keyboard solutions. If your interest lies in those areas, you should supplement this with other sources like the Keychron community forums or the GH60 subreddit for more diverse perspectives. The archive search function works but has some limitations. Keyword matching is basic and does not support Boolean operators. If you are looking for a specific feature like gasket mount or thock tuning, you will need to scan through multiple issues manually. I keep a local spreadsheet with the issue number, date, and a brief note about each project that caught my attention. This takes about five minutes per week and makes future searches much faster than relying on browser history.
Practical Tips for Getting the Most Out of It
Save the weekly PDF or HTML version locally instead of only reading in your email client. Your inbox will fill up and you will lose access to older issues. The archive page is useful but the full images and layout can break if the site changes its structure. I export each issue to a folder named by date and tag the projects I want to revisit with a simple naming convention like YYYY-MM-DD-ProjectName. This has saved me more than once when I needed to return to a build idea six months later. Pay attention to the author bios linked in each project. Experienced builders tend to have consistent quality across their work. If you find someone whose design approach matches your needs, you can follow their portfolio directly instead of waiting for the weekly to feature them again. I have built two complete keyboards from projects by a single author whose work I discovered through this digest, and both were well documented with clear instructions. The comments section on the weekly posts is often more valuable than the projects themselves. People point out firmware compatibility issues, share alternative switch options, and sometimes post updated builds that fix problems with the original design. I once found a thread where someone had ported a PCB layout to a different footprint after the original author discontinued the switches it used. That kind of community troubleshooting does not happen in the main articles but shows up regularly in the comments.
Do not ignore the non-mainstream entries. Some weeks the digest includes macro pads, numpad add-ons, and single-row keyboards alongside the usual full-size and split boards. These smaller projects are often easier to replicate and require less investment if you are testing whether custom keyboards fit your workflow. I started with a six-key macro pad before attempting a full split board, and it saved me from committing to a larger project that I was not ready to support physically.
Summary of the Process
Subscribe to the newsletter or add the RSS feed. Read the weekly issue in about fifteen minutes. Bookmark projects that interest you. Check the author's GitHub or blog for documentation completeness before starting any build. Cross-reference the comments for known issues and community updates. Save a local copy of each issue for future reference. Repeat weekly. The entire process takes less than thirty minutes and gives you a steady stream of fresh design inspiration without requiring you to maintain multiple forum accounts or bookmark lists. The real bottleneck is not finding ideas. It is deciding which ones to pursue and having the time and tools to execute them. Mechanical Keyboard Ideas Weekly handles the discovery part efficiently. The rest depends on your own skill level and project capacity. Most people only build two or three keyboards a year regardless of how many ideas they collect, so do not feel pressured to replicate everything you see. Pick the projects that solve actual problems in your setup rather than the ones that look impressive in photos.
