docs: add FAQ section for common questions#1337
Merged
Oceania2018 merged 1 commit intoSciSharp:masterfrom May 3, 2026
Merged
Conversation
Contributor
Author
|
Hi! Just following up on this documentation PR. Would love to hear your thoughts when you have a moment. Thanks! 🙏 |
Contributor
Author
|
Hi! Just following up on this PR. Would love to hear your thoughts on the FAQ section. Let me know if any changes are needed! 👋 |
Contributor
Author
|
Hi! Just following up on this PR. Would appreciate a review when you have a moment. 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a comprehensive FAQ section to the README to help new users quickly find answers to common questions about BotSharp.
Changes
Motivation
New users often have the same questions about getting started, configuring LLM providers, and deploying BotSharp. An FAQ section in the README reduces friction and directs users to the right resources.
Checklist