FILL IN THE PR DESCRIPTION HERE

FIX #xxxx (*link existing issues this PR will resolve*)

<details>

<summary><b> PR Checklist (Click to Expand) </b></summary>

<h3>PR branch</h3>

Make sure that this PR targets the main branch.

<h3>PR Title and Classification</h3>

<p>Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:</p>

<ul>

<li><code>[Bugfix]</code> for bug fixes.</li>

<li><code>[CI/Build]</code> for build or continuous integration improvements.</li>

<li><code>[Doc]</code> for documentation fixes and improvements.</li>

<li><code>[Back]</code> For changes on the ChatFAQ Back </li>

<li><code>[Admin]</code> For changes on the ChatFAQ Admin </li>

<li><code>[Widget]</code> For changes on the ChatFAQ Widget </li>

<li><code>[CLI]</code> For changes on the ChatFAQ CLI </li>

<li><code>[Chat RAG]</code> For changes on the ChatFAQ Chat RAG </li>

<li><code>[Misc]</code> for PRs that do not fit the above categories. Please use this sparingly.</li>

</ul>

<p><strong>Note:</strong> If the PR spans more than one category, please include all relevant prefixes.</p>

<h3>Code Quality</h3>

<p>The PR need to meet the following code quality standards:</p>

<ul>

<li>We adhere to <a href="https://code.with-madrid.com/en/latest/">WITH’s Coding Guidelines</a>.</li>

<li><code>black</code> and <code>isort</code> to format your code.</li>

<li>The code need to be well-documented to ensure future contributors can easily understand the code.</li>

<li>Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.</li>

<li>Please add documentation to <code>docs/source/</code> if the PR modifies the user-facing behaviors of ChatFAQ. It helps ChatFAQ user understand and utilize the new features or changes.</li>

</ul>

<h3>Notes for Large Changes</h3>

<p>Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding tests), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with <code>rfc-required</code> and might not go through the PR.</p>

<h3>What to Expect for the Reviews</h3>

<p>The goal of the ChatFAQ team is to be a <i>transparent reviewing machine</i>. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the ChatFAQ team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process: </p>

<ul>

<li> After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.</li>

<li> After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the ChatFAQ team.</li>

<li> After the review, the reviewer will put an <code> action-required</code> label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.</li>

<li> Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

</li>

</ul>

<h3>Thank You</h3>

<p> Finally, thank you for taking the time to read these guidelines and for your interest in contributing to ChatFAQ. Your contributions make ChatFAQ a great tool for everyone! </p>

</details>