BMJ Platform Overhaul — Master Execution Blueprint

planactive

Source: npp-extracted/new 58@2026-03-18_012154

BMJ Platform Overhaul — Master Execution Blueprint

Full execution blueprint for a complete overhaul, completion, audit, rewrite, and implementation roadmap for The Black Male Journal platform.

Project Context

Organization: The Black Male Journal (BMJ)

Institutional nature: A nonprofit public-benefit media and educational organization centered on Black male life, political literacy, wellness, research, journalism, cultural analysis, and institutional self-governance.

Core institutional offerings:

  • Articles, essays, and reports
  • Video content
  • Courses and workshops
  • Forums, clubs, and interest groups
  • Fee-for-service consultation
  • Membership structures
  • A future physical/in-person institutional phase

Primary service lenses:

  • Health / Wellness
  • Politics / Law
  • Culture / Philosophy
  • Technology / Entertainment
  • Business / Finance

Audience: Primarily Black boys and men, especially urban, digitally engaged cohorts roughly 16–45, with asymmetrical needs and varying levels of political, educational, legal, economic, and health-related engagement.

Institutional posture: BMJ is not just a content site. It is an interpretive institution. It should feel governed, serious, accountable, and ideologically coherent. It must communicate that Black men are stakeholders, not merely subjects of analysis.

Primary Questions This Plan Must Answer

  1. What are the next steps?
  2. What are the strongest strategic recommendations?
  3. What unresolved tasks or likely missed handoffs should be assumed from earlier partial development work?
  4. Should a single administrator — specifically the chairman — have full control over the platform?
  5. Are all links, routes, and navigation paths structured correctly, and how should they be audited and repaired?
  6. Is there consistent layout and styling across pages and templates, and what system should enforce that?
  7. Do we need a full color review and an imagery audit?
  8. Should temporary placeholders use the chairman's Instagram or LinkedIn photos and copied excerpts from his articles, and under what constraints?
  9. Are all photos, logos, user data, articles, and related assets properly stored in Supabase, and how should that be audited and remediated?
  10. What does a thorough overhaul and completion plan look like from strategy through implementation?

Non-Negotiable Brand and Visual Direction

The visual language must be rooted in revolutionary print culture, not contemporary digital minimalism.

Primary visual references:

  • 1960s–1970s liberation movement posters
  • Socialist and anti-colonial propaganda artwork
  • Radical newspapers
  • Underground press materials
  • Photocopy aesthetics
  • Screen-printing traditions

Visual traits: Halftone dot patterns, ink bleed, rough print textures, paper-like background tones, posterized portrait treatments, restricted high-impact color schemes.

Emotional and symbolic effect: Authenticity, collective identity, historical continuity with struggle, a movement tradition rather than a lifestyle brand, tangibility over digital gloss, physical presence over polished corporate smoothness, grassroots credibility, cultural memory — the feeling of a political flyer, wheat-pasted poster, or radical newspaper rather than a polished venture-backed media property.

Physical / tactile characteristics: Warm off-white paper hues, surface grain, printing flaws, rich ink texture, slightly distressed or worn edges — a site that feels printed, handled, circulated, and lived with.

This does NOT mean the product should be messy, unusable, inaccessible, or technically unsound. It means the interface system must translate tactile and political print sensibilities into a disciplined modern web system without becoming generic.

Required Plan Sections

Section 1 — Executive Diagnosis

Frank diagnosis of what is most likely wrong, incomplete, inconsistent, or at risk in a partially built BMJ platform. Categories: product definition drift, weak governance mapping, incomplete routing, page/template inconsistency, poor content modeling, unstructured media storage, weak placeholder standards, missing editorial states, unclear permissions, broken design language, absent QA/handoff documentation, lack of asset provenance rules, lack of distinction between public/member/contributor/admin experiences.

Section 2 — Assumed Missed Handoffs and Unresolved Tasks

Detailed list of likely unresolved tasks between planning, design, and engineering: page inventory not reconciled with sitemap, route names not aligned with content architecture, duplicate or dead-end navigation states, components without design tokens, layouts drifting across templates, content types not normalized, article/media metadata incomplete, contributor workflow undefined, role permissions too broad/narrow, Supabase buckets without policy clarity, placeholder assets without naming conventions, absent editorial review states, homepage not aligned with strategy, missing CTA hierarchy, no canonical image specs, unreviewed mobile layout issues, no audit trail for uploads, untracked debt from earlier iterations.

Section 3 — Governance and Platform Control

Nuanced recommendation on chairman control including risks of centralized control, benefits of emergency authority, risks of diffusion without accountability, difference between legal/editorial/platform/operational authority. Permissions matrix for: Chairman, Board-level oversight, Editor/managing editor, Contributor/writer/researcher, Media producer, Membership/community manager, Technical administrator, Super admin / break-glass emergency role.

Section 4 — Information Architecture, Routes, Links, and Navigation Audit

Complete audit framework for verifying links, routes, navigation paths. Inventory every page, route, layout, template. Identify orphan pages, route duplication. Normalize slugs and naming patterns. Separate public/member-only/contributor-admin routes. Canonical paths for all key pages. Navigation hierarchy: primary, secondary, footer, contextual, mobile, member dashboard, editorial/admin. Breadcrumb rules, CTA placement logic, internal linking strategy, redirect/404/archive rules.

Section 5 — Layout System and Visual Consistency

Framework for auditing and enforcing consistency across layouts and templates. Page shells, grid systems, content widths, section spacing, heading hierarchy, image ratios, card systems, CTA modules, quote blocks, article templates, profile pages, course/workshop pages, membership pages, directory entries, donor/support pages, admin views. Design-system enforcement model: tokens, typography scale, spacing scale, component library, template library, state guidelines, accessibility rules, editorial display rules.

Section 6 — Color Review and Image Audit

Part A — Color: Restricted palette strategy, dominant vs accent colors, print-culture references, contrast/accessibility, palette meaning and emotional role, red/black/off-white/ochre/muted gold/deep brown/faded ink blues usage guidelines. Part B — Imagery: Review chairman imagery, contributor portraits, article hero images, background textures, historical references, logos/marks, social preview images, thumbnails, member/community imagery. Temporary placeholder policy including rights considerations, brand-quality considerations, naming/tracking conventions, sunset replacement rules, alt text/metadata rules. Portrait treatment styles: halftone, duotone/posterization, cutout silhouettes, rough border treatments, archival framing, newspaper-style captioning.

Section 7 — Supabase Storage, Data, and Asset Governance

Complete audit/remediation framework for photos, logos, icons, article images, author images, PDFs, video metadata, user-uploaded assets, member data, article records, role/permission data, event/course records, forum/community data, drafts/editorial versions, backups/export logic. Clear storage model for database tables vs storage buckets, signed URLs, public/private classification, CDN caching, bucket naming, folder naming, provenance metadata, versioning, soft/hard delete, retention, audit logs, RLS, PII separation, admin-upload workflow.

Section 8 — Content Model and Editorial System

Content architecture for articles, essays, reports, videos, interviews, workshops, courses, memberships, forums/clubs, consultations, contributor profiles, chairman profile, service lenses, series, tags/topics, resources, events, testimonials, support/donation content, organizational pages. Required/optional/SEO/display/editorial-state/asset/author/visibility/member-gating fields per type. Editorial workflow states: draft → internal review → fact check → legal/sensitivity review → scheduled → published → archived → revised → withdrawn.

Section 9 — Brand Translation into Digital Experience

Typography recommendations, display vs reading type, page rhythm, paper texture usage, halftone/distress usage, iconography style, motion principles, hover/focus interaction tone, microcopy tone, social card style, article header style, PDF/report design continuity.

Section 10 — Page-by-Page Overhaul Plan

Page-by-page matrix covering: homepage, about, mission/vision/theory of change, ethics, chairman page, contributors page, articles index, single article, reports/resources, video/media, courses/workshops, memberships, forums/clubs, consultation, support/donate, contact, user account, member dashboard, admin/editorial dashboard. Per page: strategic purpose, priority audience, primary/secondary CTA, must-have sections, visual tone, content/data dependencies, likely current problems, recommended fix.

Section 11 — Implementation Phases

  • Phase 0: Discovery and audit
  • Phase 1: Governance and permissions
  • Phase 2: IA/routes/content model
  • Phase 3: Design system and visual language
  • Phase 4: Supabase storage/data cleanup
  • Phase 5: Page template rebuild
  • Phase 6: Editorial/content migration
  • Phase 7: QA and accessibility
  • Phase 8: Launch hardening
  • Phase 9: Post-launch governance and operations

Per phase: objectives, outputs, dependencies, risks, decision gates, deliverables.

Section 12 — QA, Acceptance Criteria, and Definition of Done

Route audit complete, no broken internal links, consistent layout tokens, mobile parity, accessibility compliance, asset storage normalized, metadata completeness, placeholder tracking complete, role permissions validated, admin actions logged, editorial states functional, all core page templates aligned, imagery reviewed, color system approved, launch checklist satisfied.

Section 13 — Final Recommendations

  1. Top 10 most urgent actions
  2. Top 10 structural risks if ignored
  3. Recommended governance stance on chairman control
  4. Recommended stance on placeholder imagery and article excerpts
  5. Recommended stance on Supabase storage discipline
  6. The single clearest principle governing the entire overhaul

Special Instructions

  • Chairman control: recommend a resilient institutional model, not founder absolutism or bureaucracy.
  • Placeholder photos from Instagram/LinkedIn: treat as temporary editorial assets requiring rights/provenance review, naming conventions, and replacement tracking.
  • Copied excerpts from chairman's articles: distinguish between owned editorial content, design placeholders, and attribution/source/replacement rules.
  • Visual system: living political print tradition translated into the web, not nostalgia cosplay.
  • Infrastructure: sustainable, auditable, and safe for a nonprofit institution handling users, members, contributors, and potentially sensitive data.