Run and Deploy Instructions — Content Calendar

Prerequisites

• Node.js 18 or later

Run Locally

cd delivery-package/content-calendar-track-sm/app
node server.js

Open http://localhost:3847 in your browser.

Optional port:

PORT=8080 node server.js

Two-User Test (V-5 / SC-7)

1. Start the server
2. Open http://localhost:3847 in Browser A — set team member to team-member-a
3. Open http://localhost:3847 in Browser B (or incognito) — set team member to team-member-b
4. Create and schedule an item in Browser A
5. Refresh Browser B — the same item appears in backlog and calendar

Smoke Test Checklist

• [ ] Idea Backlog: capture idea with title + channel tag
• [ ] Idea appears with status idea
• [ ] Schedule idea with publish date → status scheduled
• [ ] Editorial Calendar week view shows item on correct date
• [ ] Editorial Calendar month view shows item on correct date
• [ ] Navigate prev/next week and month
• [ ] This Week view lists scheduled items for current week
• [ ] Mark scheduled item Published
• [ ] Second browser/session sees shared data
• [ ] No OAuth, Connect Account, or Integrations screens

Run Verification

With server running:

node delivery-package/content-calendar-track-sm/scripts/run-verification.mjs

Deploy to Production

1. Copy app/ directory to your server
2. Run node server.js behind a process manager (systemd, PM2, etc.)
3. Put HTTPS reverse proxy in front (nginx, Caddy)
4. Ensure app/data/ directory is writable for persistent storage
5. Share the URL with your team

Data Location

Shared content is stored in app/data/items.json. Back up this file regularly.

Environment

No OAuth credentials or API keys required.