# Publishing

Connect your CMS, then publish approved articles at their scheduled times.

## WordPress

The guided WordPress connection asks for the site and account details. An application password comes from `RECALA_WP_APP_PASSWORD`, `--token-stdin`, or a hidden prompt. Keep it out of command arguments and logs. Connection changes require a person with the necessary company access.

```
recala connect wordpress
```

See [WordPress flags](https://recala.co/developers/cli/connect/#cmd-connect-wordpress) for noninteractive input options.

## Sanity

Connect a project, dataset and public blog URL. Map Recala signing people to author document ids in Sanity. The write token comes from `RECALA_SANITY_TOKEN`, `--token-stdin`, or a hidden prompt. The CLI does not print the supplied secret.

```
recala connect sanity
```

See [Sanity flags](https://recala.co/developers/cli/connect/#cmd-connect-sanity) for project, dataset and author mapping options.

## Verify before scheduling

Read the CMS endpoint, public site and connection state. The CLI can also report Search Console and sitemap connections. A missing optional feature or unavailable permission may appear as null rather than a successful connection.

```
recala connect status
```

```
recala cms status
```

Approval alone does not publish. Use an article’s scheduling preview to check readiness, then follow [Review an article](https://recala.co/developers/guides/review/#schedule) to save a future time.