mizcausevic-dev · mizcausevic-dev · May 7, 2026 · May 7, 2026
diff --git a/.env.example b/.env.example
@@ -0,0 +1,3 @@
+PORT=3000
+SERVICE_NAME=Content Workflow Intelligence Platform
+DEFAULT_EDITORIAL_SLA_DAYS=5
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -0,0 +1,10 @@
+## Summary
+
+- 
+
+## Validation
+
+- [ ] `npm test`
+- [ ] `npm run build`
+- [ ] no secrets or environment files committed
+- [ ] documentation and screenshots updated when applicable
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -0,0 +1,24 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+      - project/**
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [20, 24]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: npm
+      - run: npm ci
+      - run: npm test
+      - run: npm run build
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
@@ -0,0 +1,32 @@
+name: CodeQL
+
+on:
+  push:
+    branches:
+      - main
+      - project/**
+  pull_request:
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [javascript]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: github/codeql-action/init@v3
+        with:
+          languages: ${{ matrix.language }}
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: npm
+      - run: npm ci
+      - run: npm run build
+      - uses: github/codeql-action/analyze@v3
diff --git a/.gitignore b/.gitignore
@@ -0,0 +1,8 @@
+node_modules/
+dist/
+.env
+.DS_Store
+coverage/
+*.log
+content-workflow-dev.pid
+screenshots/*.html
diff --git a/README.md b/README.md
@@ -0,0 +1,223 @@
+# Content Workflow Intelligence Platform
+
+> **TypeScript portfolio project** demonstrating publishing-readiness scoring, editorial bottleneck visibility, content operations governance, and workflow-aware backend decisioning for enterprise teams.
+
+**Recruiter takeaway:** *"This person understands content operations, SEO governance, and publishing systems as coordinated enterprise workflows, not isolated tasks."*
+
+---
+
+## Project Overview
+
+| Attribute | Detail |
+|---|---|
+| **Runtime** | Node.js + TypeScript |
+| **Framework** | Express 5 |
+| **Domain** | Content operations, publishing governance, editorial workflow intelligence |
+| **Signal Areas** | Workflow age · Approval friction · Governance blockers · Search opportunity · Business priority |
+| **Operational Outputs** | Readiness posture · Bottleneck analysis · Prioritization routing |
+| **Docs** | Swagger UI at `/docs` |
+
+---
+
+## Executive Summary
+
+Content Workflow Intelligence Platform models the kind of internal service enterprise editorial, SEO, legal, compliance, and web platform teams use to move high-value content through publishing workflows with less friction and better visibility. Instead of acting like a CMS clone, the API focuses on operational readiness: where content is stuck, which teams are causing queue drag, how business priority and search upside should influence routing, and what next action an operator should take.
+
+The result is a recruiter-facing backend project that feels like a real internal publishing operations system rather than a generic content app.
+
+---
+
+## Business Problem
+
+Enterprise publishing breaks down when content, SEO, legal, compliance, and platform teams operate in separate queues without a shared operational view. High-value assets can sit in review too long, approvals get lost, schema and governance issues stay unresolved, and priority content misses the window where it would have the most business impact.
+
+---
+
+## Solution
+
+This API turns publishing workflow state into decision support. It models content items, authors, queues, approvals, blockers, and performance signals, then returns:
+
+- publishing readiness scores
+- workflow bottleneck analysis
+- prioritization routing
+- dashboard-level operational summaries
+
+---
+
+## Architecture
+
+```text
+Content item or workflow scenario
+    |
+    v
+POST /api/analyze/*
+    |
+    +--> Request validation
+    +--> Stage age and queue review
+    +--> Approval and blocker analysis
+    +--> Search opportunity and business priority weighting
+    |
+    v
+Workflow posture
+    |
+    +--> ready
+    +--> needs-review
+    +--> blocked
+```
+
+### Workflow Explanation
+
+1. Teams submit a workflow scenario or query current content inventory and queues.
+2. The service validates request shape with Zod.
+3. Readiness logic reviews stage age, pending approvals, blockers, content depth, search opportunity, and business priority.
+4. The service returns a score, issues, passed checks, and a recommended next action.
+5. Operators use dashboard, blocker, and queue views to unblock publishing and protect high-value assets.
+
+---
+
+## API Endpoints
+
+| Method | Endpoint | Purpose |
+|---|---|---|
+| `GET` | `/health` | Service status and uptime |
+| `GET` | `/api/content` | List content items |
+| `GET` | `/api/content/:id` | Fetch one content item |
+| `GET` | `/api/authors` | List authors |
+| `GET` | `/api/queues` | List workflow queues |
+| `GET` | `/api/approvals` | List approval records |
+| `GET` | `/api/blockers` | List publishing blockers |
+| `GET` | `/api/dashboard/summary` | Workflow operations summary |
+| `POST` | `/api/analyze/readiness` | Analyze publishing readiness |
+| `POST` | `/api/analyze/bottleneck` | Analyze workflow bottlenecks |
+| `POST` | `/api/analyze/prioritization` | Analyze prioritization routing |
+
+---
+
+## Sample Readiness Request
+
+```json
+{
+  "title": "Enterprise SEO Governance Platform",
+  "stage": "legal-review",
+  "daysInStage": 9,
+  "requiredApprovalsPending": 2,
+  "blockingIssues": ["missing-schema-review", "legal-copy-approval"],
+  "searchOpportunityScore": 84,
+  "businessPriority": "high",
+  "wordCount": 1180
+}
+```
+
+## Sample Readiness Response
+
+```json
+{
+  "status": "blocked",
+  "score": 40,
+  "issues": [
+    "Content has remained in the current stage beyond the expected workflow SLA.",
+    "Required approvals are still pending.",
+    "Blocking governance issues remain unresolved for this content item.",
+    "Legal review is a likely throughput bottleneck for this asset.",
+    "Schema review remains unresolved for a high-priority asset."
+  ],
+  "passedChecks": [
+    "Search opportunity supports continued prioritization.",
+    "Content depth is sufficient for target topic competitiveness.",
+    "Business priority justifies active workflow escalation if blocked."
+  ],
+  "recommendedNextAction": "Escalate approval path and route schema or legal review to the owning governance team this sprint."
+}
+```
+
+---
+
+## Screenshots
+
+### Hero Capture
+
+![Swagger UI](screenshots/01-hero.png)
+
+### Publishing Workflow and Readiness Analysis
+
+![Readiness workflow](screenshots/02-feature.png)
+
+### Bottleneck and Prioritization Proof
+
+![Prioritization proof](screenshots/03-proof.png)
+
+---
+
+## Getting Started
+
+### Prerequisites
+
+- Node.js 20+
+- npm
+
+### Setup
+
+```bash
+git clone https://github.com/mizcausevic-dev/content-workflow-intelligence-platform.git
+cd content-workflow-intelligence-platform
+npm install
+cp .env.example .env
+npm run dev
+```
+
+Visit:
+
+- `http://localhost:3000/docs`
+- `http://localhost:3000/api/content`
+- `http://localhost:3000/api/dashboard/summary`
+
+### Run Tests
+
+```bash
+npm test
+```
+
+---
+
+## What This Demonstrates
+
+- content operations translated into backend service logic
+- editorial workflow visibility and throughput thinking
+- governance-aware publishing readiness analysis
+- prioritization based on business value and search opportunity
+- production-minded TypeScript API structure with docs, tests, and operational summaries
+
+---
+
+## Future Enhancements
+
+- persist workflow entities in PostgreSQL
+- connect CMS and approval-system webhooks
+- add queue SLA tracking by team and stage
+- add publish calendar coordination and release windows
+- integrate content performance history and inventory health scoring
+
+---
+
+## Tech Stack
+
+![Node.js](https://img.shields.io/badge/Node.js-20%2B-20232A?style=for-the-badge&logo=node.js&logoColor=white&labelColor=111827&color=4ADE80)
+![TypeScript](https://img.shields.io/badge/TypeScript-5.x-20232A?style=for-the-badge&logo=typescript&logoColor=white&labelColor=111827&color=2563EB)
+![Express](https://img.shields.io/badge/Express-5-20232A?style=for-the-badge&logo=express&logoColor=white&labelColor=111827&color=F97316)
+![REST API](https://img.shields.io/badge/API-REST-20232A?style=for-the-badge&logo=fastapi&logoColor=white&labelColor=111827&color=14B8A6)
+![OpenAPI](https://img.shields.io/badge/OpenAPI-Swagger-20232A?style=for-the-badge&logo=swagger&logoColor=black&labelColor=111827&color=FACC15)
+![Zod](https://img.shields.io/badge/Validation-Zod-20232A?style=for-the-badge&logo=typescript&logoColor=white&labelColor=111827&color=8B5CF6)
+![Helmet](https://img.shields.io/badge/Security-Helmet-20232A?style=for-the-badge&logo=shield&logoColor=white&labelColor=111827&color=EC4899)
+![Supertest](https://img.shields.io/badge/Testing-Supertest-20232A?style=for-the-badge&logo=checkmarx&logoColor=white&labelColor=111827&color=22C55E)
+![License](https://img.shields.io/badge/License-MIT-20232A?style=for-the-badge&logo=open-source-initiative&logoColor=white&labelColor=111827&color=A3E635)
+
+### Portfolio Links
+
+- [LinkedIn](https://www.linkedin.com/in/mirzacausevic)
+- [Skills Page](https://mizcausevic.com/skills/)
+- [Medium](https://medium.com/@mizcausevic)
+- [GitHub](https://github.com/mizcausevic-dev)
+
+---
+
+*Part of [mizcausevic-dev's GitHub portfolio](https://github.com/mizcausevic-dev) — demonstrating enterprise publishing systems thinking, workflow governance, and backend decision support for content operations.*
diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,19 @@
+# Security Policy
+
+## Scope
+
+This repository is a portfolio project that demonstrates publishing workflow governance, editorial intelligence, and production-minded backend structure.
+
+## Supported Version
+
+The `main` branch is the supported version for review.
+
+## Reporting
+
+If you identify a security issue in the code, dependencies, or workflow configuration, please open a private report through GitHub security reporting when available or contact the repository owner directly before public disclosure.
+
+## Secure Development Notes
+
+- No production credentials belong in this repository.
+- Use `.env.example` as the reference for local configuration.
+- CI, Dependabot, and CodeQL are included to support baseline hygiene.