What You Need to Know About Working With Herb Stewart Architect Wiki
I ran into this a while back when someone recommended it for architectural reference. The actual content is spread across a few different pages and it's not always organized the way you'd expect. If you're looking at Herb Stewart Architect Wiki for the first time, start by understanding what it actually covers versus what it doesn't. The site has documentation on drafting standards, detail conventions, and some construction methodology. The indexing is rough. I found useful information buried in sections that weren't where I thought they'd be. The search function works okay but only if you use the exact terminology the author uses. Generic terms like "roof detail" won't get you far. Try the specific names of components or methods instead. One thing most people miss: the page revisions aren't clearly marked. Some pages have updates from years ago layered on top of outdated content. I learned this the hard way after following a detail that referenced a code cycle we'd already moved past. I had to cross-reference the footnotes and trace back which version of the document I was actually looking at. Check the edit history if the platform shows it, or compare against local code adoption dates to figure out what's current.
How the Reference Materials Are Structured
The wiki separates content into categories like residential framing, commercial envelope systems, and MEP coordination notes. The residential side is more complete. The commercial sections are thinner and sometimes reference sources that aren't linked anymore. If you're working on anything beyond a standard single-family project, don't assume the information will be comprehensive. Fill gaps with your own code research or local consultant input. The downloadable sheets and detail PDFs are the most useful part. They're not updated often, which is both a benefit and a problem. Benefit because the files are stable — you can reference the same drawing next year and it won't change. Problem because once something is wrong in a file, it stays wrong until someone notices. I caught an error in one of the window flashing detail sheets where the drip cap orientation was reversed. Took me about ten minutes to spot during a routine check before I started using it on a real project. I reported it through the contact form on the site. Not sure if it ever got fixed, which is another thing to keep in mind.
Common Pitfalls
People tend to treat wiki-sourced details as finished construction documents. They're not. They're reference material at best. Using them directly on a project without review against local conditions, climate zone requirements, and applicable codes is a fast way to create coordination problems. I've seen it happen. A detail for interior partition attachment looked fine on paper but didn't account for seismic bracing requirements in our zone. The fix was adding a clip schedule and adjusting the fastener pattern, which the wiki page never mentioned. Another issue is the assumption that everything on the site is accurate. It's community-maintained content. Some of it is solid. Some of it is outdated. Some of it is someone's opinion presented as fact. Verify anything that affects structural integrity, fire rating, or energy compliance through an independent source before you rely on it.
Get the Full Details
When It Actually Helps
It's useful for getting a starting point on a detail you haven't drawn before. The categorization helps you find similar assemblies. The writing style is direct — no fluff, which I appreciate. For someone who already knows how to read a construction detail, the wiki saves maybe twenty minutes per search compared to flipping through a three-volume reference set. That adds up over a project timeline. If you're new to architectural documentation, this won't teach you enough on its own. The explanations skip foundational context. You need to already understand what you're looking at for the wiki to be useful. Pair it with your local code book and a seasoned drafter's review, and it becomes a legitimate time-saver. Used in isolation, it creates more questions than answers.
