> For the complete documentation index, see [llms.txt](https://halosoft.gitbook.io/bonnita-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://halosoft.gitbook.io/bonnita-documentation/changelog.md).
# Changelog
## **Version** 1.0.1 **- December 30 2024**
#### We have updated the following features:
* **Updated:** Change the font family for theme to [**Shopify's font update notification.**](https://shopify.dev/changelog/changes-to-our-font-library)
* **Updated:** The X icon replaces the Twitter icon
#### We have improved & fixed the following features:
* **Fixed:** An issue where the main product image appeared smaller than expected on Chrome browsers.
* **Fixed:** An issue where the "Buy It Now" button text was missing. và button Buy It Now trong Product Page.
* **Fixed:** A layout issue in the "Recently Viewed Products" section that caused it to break.
* **Fixed:** some other minor issues.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://halosoft.gitbook.io/bonnita-documentation/changelog.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.