# Site-Specific Workflows

This directory is for workflows specific to this site. The core workflows in `../workflows/` cover generic SDK operations, while this folder is for site-specific procedures.

## When to Add Site Workflows

Add workflows here when you have:

- **Site-specific content patterns** - e.g., "How to add a new product to the catalog"
- **Custom block configurations** - e.g., "Setting up the featured posts carousel"
- **Multi-step business processes** - e.g., "Publishing a campaign landing page"
- **Integration procedures** - e.g., "Syncing content with the marketing site"

## Creating a Workflow

Create a markdown file following this structure:

```markdown
# Workflow: [Name]

## Purpose

What this workflow accomplishes and when to use it.

## Prerequisites

- Required access, tools, or setup
- Any content that must exist first

## Steps

1. First step with command
   ```bash
   riverbankcms ...
   ```

2. Second step
   ```bash
   riverbankcms ...
   ```

## Verification

How to confirm the workflow completed successfully.

## Rollback (if applicable)

How to undo the changes if needed.

## Notes

Any additional context or edge cases.
```

## Example Workflows

### Site-specific content creation

`create-product.md`:
```markdown
# Workflow: Create a Product

## Purpose
Add a new product to the catalog with all required fields.

## Steps
1. Create the product entry
2. Add product images
3. Link to category
4. Publish
```

### Campaign or seasonal content

`launch-campaign.md`:
```markdown
# Workflow: Launch Marketing Campaign

## Purpose
Create and publish a campaign landing page with all blocks.

## Steps
1. Create campaign page
2. Add hero with campaign messaging
3. Add product grid
4. Add CTA section
5. Preview and publish
```

## Best Practices

- Keep workflows focused on one task
- Include all commands needed (copy-pasteable)
- Document site-specific field requirements
- Reference the CLI reference for command details
- Update workflows when the site schema changes
