# RateRight Content Engine - Quick Start Guide

## Immediate Implementation (Today)

### 1. Create Directory Structure
```bash
mkdir -p /home/ccuser/rateright-growth/rivet/content-engine/{config/templates,data/{drafts/{linkedin,blog,case-studies},photos,competitor-data,published},scripts,logs}
```

### 2. Set Up First Cron Job (Competitor Monitoring)
Create file: `/home/ccuser/rateright-growth/rivet/content-engine/scripts/competitor-monitor.sh`
```bash
#!/bin/bash
DATE=$(date +%Y-%m-%d)
LOG_FILE="/home/ccuser/rateright-growth/rivet/content-engine/logs/content-engine.log"
DATA_DIR="/home/ccuser/rateright-growth/rivet/content-engine/data/competitor-data"

echo "[$(date)] Starting competitor monitoring" >> $LOG_FILE

# This will be called by Clawdbot cron job
# Actual monitoring done via web_fetch tool
```

### 3. Create LinkedIn Templates
Create: `/home/ccuser/rateright-growth/rivet/content-engine/config/templates/linkedin/industry-insight.md`
```markdown
# [Industry Trend/Update]

[2-3 sentences explaining the trend and its impact on construction hiring]

**Why this matters for construction businesses:**
- [Point 1]
- [Point 2] 
- [Point 3]

**How RateRight helps:**
[Brief explanation of how RateRight addresses this trend]

#construction #hiring #australia #[specific-trade] #[location]
```

### 4. Test Image Analysis
Take a sample construction photo and test:
```bash
# Save photo to: /home/ccuser/rateright-growth/rivet/content-engine/data/photos/test.jpg
```

## Cron Jobs to Set Up in Clawdbot

### Job 1: LinkedIn Content Generator
- **Name:** `linkedin-content-mwf`
- **Schedule:** `0 9 * * 1,3,5` (9 AM Mon, Wed, Fri)
- **Prompt:** "Generate LinkedIn post for RateRight. Choose: industry insight, hiring tip, or testimonial. Include #construction #hiring #australia. Save to /home/ccuser/rateright-growth/rivet/content-engine/data/drafts/linkedin/"

### Job 2: Daily Competitor Check
- **Name:** `competitor-check-daily`
- **Schedule:** `0 6 * * *` (6 AM daily)
- **Prompt:** "Check Workmate, Sidekicker, Airtasker, HiPages websites for changes. Save findings to /home/ccuser/rateright-growth/rivet/content-engine/data/competitor-data/"

### Job 3: Weekly Blog Generator
- **Name:** `blog-generator-weekly`
- **Schedule:** `0 10 * * 0` (10 AM Sunday)
- **Prompt:** "Generate SEO blog post about construction hiring in Australia. Target keywords: construction hiring australia, labour hire sydney. Save to /home/ccuser/rateright-growth/rivet/content-engine/data/drafts/blog/"

### Job 4: Approval Reminder
- **Name:** `approval-reminder-daily`
- **Schedule:** `0 17 * * *` (5 PM daily)
- **Prompt:** "Check drafts folder and send Telegram message to Michael with pending content for approval."

## Photo Pipeline Setup

1. **Photo Directory:** `/home/ccuser/rateright-growth/rivet/content-engine/data/photos/`
2. **Manual Trigger:** When Michael adds a photo, run:
   ```
   Analyze this construction photo and generate LinkedIn post draft. Save to drafts folder.
   ```
3. **Auto-trigger (Future):** File watcher script

## Content Approval Workflow

1. **Drafts Created:** → `/content-engine/data/drafts/`
2. **Notification Sent:** Telegram to Michael at 5 PM daily
3. **Michael Reviews:** Reads drafts, approves/rejects
4. **If Approved:** Move to published folder, post to LinkedIn
5. **If Rejected:** Move to archive, note reason

## First Week Checklist

- [ ] Create directory structure
- [ ] Set up 4 cron jobs in Clawdbot
- [ ] Create 5 LinkedIn templates
- [ ] Create 1 blog template
- [ ] Test image analysis with sample photo
- [ ] Test competitor monitoring
- [ ] Set up Telegram notifications
- [ ] Create first batch of content drafts

## Expected Output Week 1

- 3 LinkedIn post drafts
- 7 competitor monitoring reports
- 1 blog post draft
- Telegram approval system working
- Photo analysis tested

## Tools Being Used

1. **web_search** - Industry research
2. **web_fetch** - Competitor monitoring
3. **image** - Photo analysis
4. **exec** - File management
5. **message** - Telegram notifications
6. **cron** - Scheduling

No external APIs needed for initial implementation.