# Create your first site

Source: https://zotonic.com/docs/1527/create-your-first-site

URI: https://zotonic.com/id/1527

Language: en

Create the garden blog, open it in your browser, and sign in to its admin.

Start with a running Zotonic node from [your installation route](/id/1526). Run the commands below from the repository root, inside the container or Nix shell if you chose one.

1. Create the example site
--------------------------

```sh
bin/zotonic addsite -s blog -H garden.test garden
bin/zotonic status
```

The command creates `apps_user/garden`, prepares the database schema, compiles the application, and starts it on the running node. Expect `garden` to reach the running state. Keep the generated admin password shown in the output; you need it for the next step.

2. Give your browser the local hostname
---------------------------------------

On the computer running your browser, add this line to its hosts file using an administrator-enabled text editor:

```text
127.0.0.1 garden.test
```

The file is `/etc/hosts` on macOS/Linux and `C:\Windows\System32\drivers\etc\hosts` on Windows. For containers, edit the computer's hosts file, not just the container's. Keep any existing entries. You can skip this step if your local DNS already resolves `garden.test` to this machine.

3. Open the site and admin
--------------------------

Open [your garden site](https://garden.test:8443/) in the browser. These examples use the default development HTTPS port 8443; use your configured port if different. Expect the blog home page. The generated development certificate may need a local browser exception.

Open [the garden admin](https://garden.test:8443/admin) and log in as **admin**, using the password printed by `addsite`. These are your site's credentials, separate from the status site's `wwwadmin` account.

4. Make your first change
-------------------------

Open `apps_user/garden` in your editor, then follow [Change a template and see the result](/id/2915). There is no need to create a custom module first.

If the wrong site opens, check the hosts entry and `priv/zotonic_site.config` hostname. If creation fails, read the error and inspect the partially created directory before retrying. Native database problems can be checked with [Prepare local PostgreSQL](/id/3045); containers use database host `postgres`. See [addsite options](/id/3005) for a non-default configuration.

Site configuration and enabled modules
--------------------------------------

A site is identified by its application and `priv/zotonic_site` configuration. Supported formats include Erlang `.config`, JSON, and YAML; follow the format already used by the project.

For Erlang configuration, the file is a list of terms ending with a period:

```erlang
[
    {enabled, true},
    {environment, development},
    {hostname, "garden.test"}
].
```

This is a small fragment illustrating syntax, not a replacement for the generated database and module settings.

Inspect the actual configuration sources with `siteconfigfiles garden` and `siteconfig garden`. A site's installation module list and its current activation state are different concerns, especially on database-backed sites. Verify enabled modules in the admin or module manager.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/1527?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/1527?language=en>)
