---
url: /en/docs/workflows/simple.md
description: >-
  Implement a simple workflow in Sveltia CMS for direct content editing without
  review.
---

# Simple Workflow

This is the default remote workflow suitable for single users or small projects. There would be no review process, and changes are made directly to the repository.

## Use Cases

* Individual bloggers or content creators managing their own websites.
* Small teams or projects where a formal review process is unnecessary.
* Quick content updates or changes that do not require oversight.

## Requirements

No special requirements are needed to use the simple workflow. Users can start making changes directly after setting up their Sveltia CMS instance.

## Configuration

No specific configuration is required for this workflow. It’s used when the top-level `publish_mode` option is omitted, set to `simple` or set to an empty string. A collection can override it with its own [`publish_mode`](/en/docs/workflows/editorial#enabling-the-workflow-per-collection) option.

## Workflow

The simple workflow allows users to create, edit, and delete entries directly in the connected Git repository without any review process. Here’s how it works:

1. Log in to Sveltia CMS using the standard OAuth authentication process or an access token.
2. Navigate to the desired collection from the collection list.
3. Create, edit, or delete entries as needed.
4. Save the changes. Sveltia CMS will automatically commit and push the changes to the connected Git repository.

## Deploying Changes

Changes made through Sveltia CMS are automatically committed and pushed to the connected repository’s default branch (e.g., `main` or `master`, unless the `branch` option is set). If you have set up CI/CD for your site, the changes will be deployed automatically based on your existing deployment process.

See the [deployments guide](/en/docs/deployments) for more details, including how to disable automatic deployments if needed.

::: tip Pull CMS Changes to Your Local Repository

Sveltia CMS commits changes to the remote repository, not to the copy on your computer. To see content published in the CMS on your local development server, run `git pull` first. Pulling before you make your own changes also helps avoid merge conflicts when you push. This doesn’t apply to the [local development workflow](/en/docs/workflows/local), where the CMS writes to your local files instead.

:::

## Multiple Editors

While this workflow is designed for single users, multiple editors can still collaborate by coordinating their changes. However, since there is no review process, it is essential to communicate effectively to avoid conflicts and ensure that everyone is aware of the changes being made.

At this time, Sveltia CMS does not provide built-in features for handling merge conflicts or simultaneous edits. We plan to add such features in future releases to enhance collaboration in the simple workflow.