Subsets Documentation Site Manager

Expert assistant for maintaining and extending the Subsets documentation website, a Docusaurus-based technical documentation site for an AI-driven retention experimentation platform.

What This Skill Does

This skill helps you work with the Subsets documentation site by:

Project Context

**Subsets** is an AI-driven retention experimentation and automation platform for subscription businesses. The documentation site explains data connections, delivery formats, and marketing automation integrations.

**Tech Stack:**

Instructions

1. Understand the Site Structure

Before making changes, familiarize yourself with:

```

docs/ # All documentation content

├── overview.md # Routes to / (main landing)

├── Data Connections/ # Integration methods

├── Data Delivery/ # Format specifications

└── Integrations/ # Marketing tool integrations

├── braze.md

├── hubspot.md

├── iterable.md

├── onesignal.md

├── piano.md

├── responsys.md

├── sailthru.md

└── blueconic.md

docusaurus.config.ts # Main site configuration

sidebars.ts # Navigation structure

src/css/custom.css # Custom styling

```

2. Adding New Documentation

When creating new documentation pages:

1. **Create the Markdown file** in the appropriate `docs/` subdirectory

2. **Add frontmatter** for sidebar positioning:

```markdown

---

sidebar_position: 3

---

# Page Title

```

3. **Update `sidebars.ts`** if adding new sections or categories

4. **Follow existing patterns** - review similar pages for tone and structure

5. **Test locally** before committing:

```bash

yarn start

```

3. Content Standards

Maintain these standards across all documentation:

4. Development Workflow

Use these commands for common tasks:

```bash

Start development server (hot reload enabled)

yarn start

Type checking (run before committing)

yarn typecheck

Build for production (test before deployment)

yarn build

Serve production build locally

yarn serve

Clear cache if experiencing issues

yarn clear

```

5. Configuration Changes

When modifying site configuration:

6. Quality Assurance

Before committing changes:

1. **Run type checking**: `yarn typecheck`

2. **Test locally**: `yarn start` and manually verify changes

3. **Validate links**: Configuration throws on broken links automatically

4. **Check responsive design**: Test on different screen sizes

5. **Build test**: Run `yarn build` to ensure production build succeeds

6. **External links**: Verify any external integration links are current

7. Troubleshooting

Common issues and solutions:

8. Deployment

Deployment is automatic via GitHub Actions:

9. Content Organization

The three main content areas:

**Data Connections** (`/data-connections/`): Methods for connecting external data sources to Subsets platform

**Data Delivery** (`/Data%20Delivery/`): Specifications and formats for delivering data samples, including behavioral data

**Integrations** (`/integrations/`): Marketing automation tool integrations (Braze, HubSpot, Iterable, OneSignal, Piano, Responsys, Sailthru, BlueConic)

10. Best Practices

Example Usage

**Adding a new integration:**

1. Create `docs/Integrations/new-tool.md`

2. Add frontmatter with appropriate `sidebar_position`

3. Write integration steps following existing integration page patterns

4. Update `sidebars.ts` if needed

5. Run `yarn typecheck && yarn build` to validate

6. Test locally with `yarn start`

7. Commit and push to `main` for automatic deployment

**Updating existing documentation:**

1. Read the current page with the Read tool

2. Make targeted edits using the Edit tool

3. Run `yarn start` to verify changes

4. Run `yarn typecheck` before committing

5. Commit and push to `main`

Important Notes