Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Love it. Check out “Writing for GOV.UK”[0] for more guidance.

Among interesting things to note that they strongly discourage FAQs (“if you write content by starting with user needs, you will not need to use FAQs … they are usually not frequently asked questions by the public, but important information dumped by the content editor”). The concept of FAQ has long been a pet peeve of mine, although I do believe the “question and answer” format has some merit.

[0] https://www.gov.uk/guidance/content-design/writing-for-gov-u...



A useful FAQ list must consist of questions that are actually often asked.

They represent discovered problems in the text the author didn't foresee.


> They represent discovered problems in the text the author didn't foresee.

Indeed. If certain questions are asked frequently, likely the information is not presented with audience’s actual needs in mind. Content should be updated, possibly rewritten. Putting up a FAQ shows content editor washing their hands of that responsibility.

I also find it a little rude, like “Welcome to the group of people who, despite our best efforts, didn’t manage to understand what we wrote! Here are some questions you lot keep asking…” (Of course, usually it’s not that, but rather a half-hearted attempt to be helpful and/or reduce the amount of people getting in touch with questions.)


Of course, FAQs originated in places like mailing lists and usenet groups, where it's arguably a good fit, precisely because there is no real standing body of text. The trouble is that it then got shoe-horned into being used on websites.


I think FAQs are an excellent way to present information— even information that has been previously covered— in a different way. Not everybody absorbs the same way, and not all information is presented clearly.


Perfectly-timed!


Indeed!




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: