# Writer Quickstart

URL: /bengal/docs/get-started/quickstart-writer/
Section: get-started
Description: Create your first site and start writing content

---

> For a complete page index, fetch /bengal/llms.txt.

Create your first Bengal site and publish content in 5 minutes. No theming or code required.

## Prerequisites

:::{checklist} Before You Start
:show-progress:
- [x] Basic Markdown knowledge
- [ ] [[docs/get-started/installation|Bengal installed]]
- [ ] Terminal access
:::{/checklist}

## Create Your Site

```bash
bengal new site myblog --template blog
cd myblog
```

The `--template blog` flag scaffolds a complete blog structure with sample posts. Other templates: `default`, `docs`, `portfolio`, `product`, `resume`.

:::{dropdown} Or use a custom skeleton YAML
:icon: file-text

Define your site structure in one YAML file:

```yaml
name: My Blog
structure:
  - path: index.md
    type: blog
    props:
      title: My Blog
    content: |
      # Welcome to My Blog

  - path: posts/hello-world.md
    type: blog
    props:
      title: Hello World
      date: "2026-01-15"
    content: |
      # Hello World
      My first post!
```

Apply it:

```bash
bengal project skeleton apply my-blog.yaml
```

See [[docs/tutorials/sites/skeleton-quickstart|Skeleton YAML Quickstart]] for more examples.
:::

## Start the Dev Server {#dev-server}

:::{target} hot-reload
:::

```bash
bengal serve
```

Your browser opens automatically at `http://localhost:5173/`. The server rebuilds on save—CSS changes apply instantly without page refresh.

## Create Your First Post

```bash
bengal new page my-first-post --section posts
```

This creates `content/posts/my-first-post.md`. Edit it:

```markdown
---
title: My First Post
date: 2026-01-15
tags: [welcome]
description: Getting started with Bengal
---

# My First Post

Welcome to my blog! Bengal makes publishing simple.

## What's Next

- Add more posts with `bengal new page`
- Customize your theme
- Deploy to the web
```

**Save.** The page appears instantly in your browser.

## Customize Your Site

Edit `config/_default/site.yaml`:

```yaml
site:
  title: "My Awesome Blog"
  description: "Thoughts on code, design, and life"
  language: "en"
```

:::{dropdown} Other config files
:icon: settings

Bengal splits configuration across focused files in `config/_default/`:

| File | Purpose |
|------|---------|
| `build.yaml` | Parallel builds, output directory |
| `theme.yaml` | Theme selection and options |
| `features.yaml` | Search, RSS, sitemap toggles |
| `content.yaml` | Markdown processing options |

See [[docs/building/configuration|Configuration Reference]] for details.
:::

## Build and Deploy

```bash
bengal build
```

Output goes to `public/`. Deploy to any static host:

| Platform | Build Command | Output |
|----------|---------------|--------|
| Netlify | `bengal build` | `public` |
| Vercel | `bengal build` | `public` |
| GitHub Pages | `bengal build` | `public` |

Bengal auto-detects Netlify, Vercel, and GitHub Pages to set `baseurl` automatically. See [[docs/building/deployment|Deployment Guide]] for CI/CD workflows.

## Frontmatter Essentials {#frontmatter}

Every page starts with YAML frontmatter:

```yaml
---
title: Page Title           # Required
date: 2026-01-15            # Publication date (ISO format)
description: SEO text       # Search/social preview
tags: [tag1, tag2]          # Taxonomy
draft: true                 # Exclude from production
---
```

:::{dropdown} All frontmatter fields
:icon: list

| Field | Description |
|-------|-------------|
| `title` | Page title (required) |
| `date` | Publication date (ISO format) |
| `description` | SEO/social preview text |
| `tags` | Taxonomy tags (e.g., `[python, web]`) |
| `weight` | Sort order in section (lower = first) |
| `draft` | `true` excludes from production builds |
| `slug` | Custom URL (overrides filename) |
| `type` | Page type for template selection |
| `variant` | Visual presentation variant |
| `lang` | Language code (`en`, `es`, etc.) |
| `nav_title` | Short title for navigation |
| `aliases` | Redirect URLs to this page |

Custom fields are accessible in templates via `page.props.fieldname`, `page.params.fieldname`, or `page.metadata.fieldname` (all equivalent).
:::

## Next Steps

- **[[docs/content/authoring|Content Authoring]]** — Markdown features and syntax
- **[[docs/content/organization|Content Organization]]** — Structure your site
- **[[docs/theming|Theming]]** — Customize appearance
- **[[docs/tutorials/sites/build-a-blog|Build a Blog]]** — Complete tutorial