added-faq-ui #30
Open
added-faq-ui #30
Conversation
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
|
Another pull request! I see you've used React here. Just make sure the website doesn't become too heavy to load. it's meant to be a simple showcase site built with HTML, CSS, and JavaScript. |
|
@sandhya-tomar are you still working on this issue? if not then we can close this |
|
@VrajVed Yes, you can close this.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Added new FAQ data to faqs.json to improve the bot’s response quality and keep the questions up to date for users.
Approach:
Located faqs.json.
Appended verified and relevant questions/answers.
Maintained correct JSON format and indentation.
Linked Issue:
This PR addresses dynamic FAQ loading (if there’s an issue number, mention like: Closes #12).
Screenshot:
No UI changes made. This update only modifies the FAQ data (JSON file), so no screenshots are required.
✅ Checklist:
I have committed the updated FAQ content.
No merge conflicts.
JSON is valid and consistent with the existing format.
Linked to an issue or improvement.