> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Site settings

> Manage a site's name, knowledge, and lifecycle.

Open **Settings** from the site header, then choose **General**. On a smaller screen, open the Settings tab and select **General**.

![General settings for the Portico Journal site in Fimo Studio](https://assets.fimo.ai/cdn-cgi/image/width=1280,fit=scale-down,quality=85,format=auto/docs/studio/studio-project-settings-20260825.png)

## Site knowledge

Use **Knowledge** in site settings to save website goals, audience, brand guidance, and rules.
Think of site knowledge as a shared brief for your agents, rather than content written for your website’s visitors.
For example:

> We help small businesses manage their finances. Write for business owners, not accountants. Keep the tone friendly and direct, explain financial terms, and avoid promising specific savings.

This guidance is shared across Branches and becomes available to agents on their next context refresh.
Managers can edit it; agents may save changes only when explicitly asked and authorized.
Reading or editing knowledge requires the corresponding site permission.
Knowledge included in a chat follows the same chat access rules as other tool results.

**Draft from website** analyzes code, labels, and sampled CMS copy from the default Branch in the background. It produces a Markdown brief covering Brand, Target, Goals, Rules, Competitors, Tone of voice, and Design preferences. Missing information is marked “Not specified.” Code is pinned to a revision; CMS content is sampled when the run executes and may be unpublished. It does not crawl the live website. Edit the proposed guidance in the knowledge field, then choose **Save**. Drafting
alone never changes saved knowledge. Check inferred goals carefully: the current website may not
reflect your intended direction. If analysis fails, retry it.

Knowledge is optional. An empty knowledge base does not prevent agents from working. Each save
replaces the current Markdown. Keep this brief up to date as your business and brand evolve.

For command-line access, see [Site knowledge](/docs/cli/knowledge.md).

## Other General settings

* **Site display name** changes the name shown across Studio.
* **Unpublish** removes public access without deleting site data.
* **Duplicate site** creates a copy in the current organization. The copy's `.fimo/project.json` links to the new site, so agents and `fimo` commands in the copy act on the copy, not on the original.
* **Delete site** permanently removes the site and its data. Organization owners and admins can also delete a site whose setup did not finish.

Only site members with permission to manage the site can change these settings.

## Languages

Open **Languages** to add supported languages, choose the default, and review content and label coverage for each language.

You can also ask Fimo, in Studio chat or in Slack, to add a language, for example before translating a page. Choosing the default and removing a language stay here.

Changing the default does not move or translate existing content. It changes the language Fimo uses when no locale is specified. If the default language has no URL prefix, unprefixed pages switch to the new default and the previous default receives its language prefix. Republish afterward to update the published routes and SEO defaults.

Removing a language permanently deletes its localized content and labels. The current default language is protected; make another language the default before removing it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.