Enterprise Content Management System

A content management system where authors, editors and publishers each have the right permissions across business units. Pages render in under 60ms and pass a full security audit.

A publishing system for large teams: clear approval steps, fast pages and a full record of every change.

Editorial teams across several business units published to multiple publications. Each needed its own approval chain, and changes had to be traceable after the fact.

Corporate editorial teams required granular publishing approval workflows with distinct permissions for authors, editors, and publishers across multiple publications.

• •Model author, editor and publisher permissions per business unit.
• •Serve pages fast from cache while keeping published changes visible immediately.
• •Make custom rich-text content safe to render.

I architected the Laravel core and permission model, the Redis caching and invalidation strategy, the audit log, and the content sanitization, and worked on the Vue.js editor and workflow screens. The stack ran in Docker.

Architected modular Laravel core with Vue.js frontend, multi-level Redis content caching, and automated audit logs tracking every content modification.

1. 01

   Vue.js editor and workflow

   WYSIWYG editing, review queues per role, and a publishing panel that shows where each article sits in the chain.

2. 02

   Laravel modular core

   Articles, publications, business units and roles as separate modules, with publishing done in a single database transaction.

3. 03

   Redis multi-level cache

   Article pages and feeds cached with tags, so a publish can flush exactly the article and its category.

4. 04

   Audit log

   Every create, update, publish and role change written alongside the content change in the same transaction.

• •Nested permission hierarchies across business units.
• •Surgical cache invalidation on publish with a 96.4% cache hit ratio.
• •A full audit trail of content and role changes.

// Hierarchical Content Publishing Workflow with Automatic Cache Flush
public function publishArticle(Article $article, User $editor) {
    DB::transaction(function () use ($article, $editor) {
        $article->update([
            'status' => 'published',
            'published_at' => now(),
            'approved_by' => $editor->id
        ]);
        Redis::del("cache:articles:{$article->slug}");
        Redis::tag(['articles_feed', "category:{$article->category_id}"])->flush();
        AuditLog::create(['action' => 'PUBLISH', 'target' => $article->id, 'user_id' => $editor->id]);
    });
}

1. 01

   Complex nested permission hierarchies across multiple corporate business units.

   A role and unit hierarchy evaluated in policies, so a user can be an editor in one unit and an author in another.

2. 02

   Dynamic page asset caching with immediate surgical cache invalidation on publish.

   Tagged Redis caching with targeted flushes for the article and its category inside the publish transaction.

3. 03

   Preventing XSS and SQL injection across custom WYSIWYG markup rendering.

   Server-side sanitization of WYSIWYG markup and parameterized queries throughout, which kept the security audit at 100% pass.

Security

Role policies on every action, sanitized rich text to prevent XSS, parameterized queries against SQL injection, and an immutable audit log.

Speed & growth

Pages render in under 60ms thanks to multi-level Redis caching, while targeted invalidation keeps published content fresh.

Policy tests cover each role in each unit. Sanitization is tested against known XSS payloads, and publish flows are tested to confirm the right cache tags are flushed.