# Quickstart

From zero to a published post on your domain. Budget ten minutes; most of it
is a DNS record propagating.

::::steps

:::step[Create your workspace]
Sign up, name your organization. You land in the dashboard.
:::

:::step[Add your site]
**Sites → Add site**, enter your domain (e.g. `example.com`). baas issues a
verification token and a public key (`pk_…`) for that site.
:::

:::step[Verify ownership]
Add either a DNS `TXT` record on `_baas.example.com` containing the token,
**or** serve the token at `https://example.com/.well-known/baas-verify.txt`.
Click **Verify**. Details and troubleshooting:
[Site verification](/docs/verification).
:::

:::step[Let the profiler work]
On verification baas crawls your site and fills in your **content profile**
(industry, audience, tone) and proposes **link targets** from your
navigation. Review both on the site page — rank the money pages highest and
prune anything you don't want linked.
:::

:::step[Create a blog]
On the site page, create a blog with a base path (default `/blog`). This is
the path the blog lives under on *your* domain.
:::

:::step[Generate your first post]
Hit **Generate now** on the blog page. The pipeline plans a topic, drafts
the article, weaves in backlinks, and writes SEO metadata — a few minutes
end to end. The post appears as *pending review*.
:::

:::step[Review and publish]
Open the post: full preview, the backlinks it carries, and the generation
trace. Click **Approve & publish**.
:::

:::step[Put the blog on your site]
Pick an integration — one script tag is enough to start:

```html
<div data-baas-blog data-key="pk_YOUR_KEY" data-base-path="/blog"
     data-api="https://api.dailysmith.com"></div>
<script src="https://api.dailysmith.com/v1/sdk/blog.js" async></script>
```

For crawler-grade SEO, add an [edge proxy rule](/docs/install-proxy) or
[static prerender](/docs/install-prerender) on top.
:::

::::

:::callout{severity=success title="You're live"}
Set a [publishing schedule](/docs/content-pipeline) so new posts arrive in
your review queue automatically, and skim the [topic queue](/docs/content-pipeline)
to approve the briefs you want written next.
:::