> For the complete documentation index, see [llms.txt](https://docs.nitroapps.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nitroapps.co/lumise/settings/settings.md).
# Settings
**In General Tab** You can change the logo,URL, site title, Favicon, theme color
*Result:*
**In Editor tab** You can change some settings on **Customer end**
**In Shop tab**\
You can do setting to comply with the currency rule in your country
\
**In Google font tab**\
You can set a number of font to show on Customer end
**In Shopify tab**
### **Language**
To set up Language for both **Customer end** and **Store Owner end**, firstly, please click on **Language** on the **left sidebar**
Click on **Add new language**
Select a **flag icon according to your language**
Create **translations**
**Search** text function
Go back to **Settings-> Language**
After saving you will see a **option** for new languages appear here
---
# 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://docs.nitroapps.co/lumise/settings/settings.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.
