> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/getting-started/initial-configuration.md).

# Initial Configuration

The settings worth changing before you go live.

The order below is deliberate: each step builds on the one before.

## 1. Identity

**Site Management → Identity & Content**

Set your company name, tagline, logo, favicon and link-preview image, then your public contact details and social profiles.

The company name appears in the site header, the footer, the dashboard sidebar, page titles and the sender name on email. Setting it here changes all of them.

## 2. Appearance

**Site Management → Appearance**

Colours, fonts, corner radii and background treatment, with a live preview. Start from a preset and adjust.

Changes are versioned — if you dislike a change you can roll it back.

## 3. Features

**Site Management → Features**

Switch off what you do not need. A studio with no shop turns off Store, Payments, Customers and Reviews; the navigation, routes and page-builder blocks for those disappear cleanly.

Nothing is deleted. Turning a feature back on restores it as it was.

## 4. Email

**Site Management → Email**

Until this is configured, the platform cannot send password resets, order confirmations or enquiry replies.

Enter your SMTP host, port, username, password and encryption, plus the sender name and address recipients will see. Send a test message before moving on.

## 5. Navigation

**Site Management → Navigation**

Build your header and footer menus. Pages are picked from a list, so a renamed page updates its menu entry automatically.

## 6. Pages

**Site Management → Pages**

A fresh installation ships with a home page, a contact page and a few others. Edit them in the page builder, or create your own.

## 7. Store, if you are selling

**Store → Settings** — currency, store country, tax and shipping.

{% hint style="warning" %}
Set the **currency** before creating products. Prices are stored in the currency's minor units, and changing currency later does not convert existing prices.
{% endhint %}

Then **Payments → Settings** to configure a provider.

## 8. Roles

**Administration → Roles**

Before inviting colleagues, decide what each role can do. Grant the narrowest role that lets someone do their job.

Keep the **Owner** role to as few people as possible — it reaches everything, including the database connection settings.

## 9. Your colleagues

**Administration → Members**

Add people and assign roles.

## 10. Before going live

* `APP_DEBUG=false` in `.env`
* HTTPS enabled
* `SESSION_SECURE_COOKIE=true`
* Backups configured **and a restore tested**
* Demo content removed, if you installed it

The **Production Checklist** covers this in full.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hollow-peak.gitbook.io/docs/getting-started/initial-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
