The Facts about FAQs
summary
FAQs originate on Usenet as Q&A documents meant to cut repetition and they serve readers who want quick, task‑oriented answers rather than deep overviews. Common failures are disorganization, staleness, duplicated content, questions not in users’ words, and bloated answers. Fixes are concrete: assign a single owner with a review cadence, avoid duplication by linking or using includes, organize by user type or procedure, and add an expand or collapse all control so Ctrl‑F still works. Use FAQs as a planning tool, not a dumping ground.
AI-written summary · about
chapters (4)
related talks
31mDesign FAQs from 5 Years of Coaching FOSS Projects
20mStop writing docs; Start helping
40mHow to Write Documentation for People That Don't Read
40mThe art of asking questions
31mSurviving Support: 10 Tips for Saving Your Users and Yourself
43mThe 7 Deadly Sins of Documentation
46mThe 7 Deadly Sins of Documentation
29mSearch-First Writing for Developers