I’m exploring ways to use Obsidian as a tool for managing FAQs (Frequently Asked Questions). My goal is to create a structured, searchable knowledge base where questions and answers can be easily updated and linked. I’d love to hear from the community about:
The best plugins or core features for FAQ management (e.g., Dataview, Templater, or others).
Recommended note structures (one note per question vs. grouped notes).
I recommend experimenting with different approaches with a small set of notes to see how they feel. I would lean towards a question per note so you can use the quick switcher (filename search) instead of the full search, but it’s entirely possible that some groups of related questions may make more sense grouped together in notes. Mainly you’ll want to think about how you’re likely to access the info.
I don’t think you need any plugins, unless you encounter friction that can’t be solved with the core app.
Also, frequently asked questions by who? And answers for who? What/where is the target for this?
Are you publishing this out somewhere, with Obsidian Publish, or some other tool? Is it for customers/clients/students? Or is this an internal knowledge-base for you, or a team?
(Some of those answers might impact the recommendations.)
The FAQs are designed for higher education students and should prioritize clarity, practical examples, and links to deeper resources. We also plan to publish them on a website, with appropriate access protection to ensure that only authorized users can view the content.
In that case, in terms of structure I’d search the web for general info about / best practices for making FAQs. Here’s a little blurb about that from a well known usability firm:
The traditional question list followed by the individual questions and answers is still the best underlying design for short and medium-length (less than 10-page) FAQs.
For longer FAQs, or those with involved answers, screenshots, or alternatives, a separate list of questions that lead to answer pages (or topic pages) works best.