Schema
Platform accounts
Connection status, identifiers, and token metadata stay in one record per provider.
Tracks connection and health state
Supports refresh and sync flows
Feeds admin platform management
Backend Delivery
The platform hub that connects content, admin control, and public pages.
This route makes the backend visible as a product capability: connectors, storage, public APIs, and operator surfaces all organized in one place.
Route stats
Connector targets
4
GitHub, LinkedIn, Meta, and X modeled under one contract
Public routes
3+
Safe payloads exposed for homepage, showcase, and route modules
Admin surfaces
4
Overview, platforms, showcase, and sync logs
Directory
Cross-platform delivery
Ecosystems
A connected view of the products, surfaces, and channels that shape the portfolio.
Managed showcase
Projects
Backend-fed project stories curated from the unified public showcase layer.
Applied intelligence
AI Core
AI modules, context assembly, and workflow patterns tied to real portfolio operations.
Spotlight
Backend outcome
The portfolio now has a foundation for public storytelling, operator control, and future automation work.
Database
MariaDB ready
Admin
Protected routes
Public pages
Backend-fed
Connector Stack
Normalized models behind the public experience
The hub is more than a theme change. It creates a reusable data contract for account status, sync runs, profiles, content, and showcase curation.
Data
Profiles and content
Latest platform snapshots and content items are persisted so the site can render without direct client-side API dependencies.
Profile snapshots per provider
Normalized content items for reuse
Prepared for richer filters and archives
Publishing
Showcase curation
Public work is selected from managed showcase records rather than repeated hardcoded arrays.
Visibility toggles and ordering
Reusable across home and route pages
Supports future campaign or spotlight modules
Ops
Sync observability
Sync runs capture operational state so connector failures are visible and recoverable.
Running, success, and failed states
Error capture per sync run
Useful base for scheduled jobs later
Public Delivery
APIs and routes serving the portfolio
The pages added in this task are structured to consume backend-friendly data instead of inventing their own isolated content models.
API
Site data endpoint
Core identity, metrics, showcase items, and platform summaries are exposed through a single safe public payload.
Supports the homepage provider
Backed by normalized records
Keeps provider secrets off the client
Feed
Showcase endpoint
The public showcase feed can be consumed by future sections, alternate frontends, or partner embeds.
Admin-approved entries only
Simple public data contract
Portable beyond the homepage
Pages
Hub route content
The new route collection is powered by a dedicated public hub content builder, giving navigation pages a coherent backend-aware story.
Ecosystems, projects, AI core, and platform hub
Derived from portfolio data plus curated fallbacks
Ready for future CMS or admin-driven expansion
Operator Surfaces
Protected tools for managing the public narrative
These are the control points behind the public site and a strong base for future automation.
Dashboard
Overview dashboard
A single operational snapshot of connector health, sync recency, and high-level metrics.
Fast status check
Useful for daily monitoring
Sits inside the same app as public routes
Connectors
Platform connections
Manage provider credentials, reconnect flows, and manual sync actions in one place.
Manual connect and sync flow
Health messaging per provider
Prepared for future OAuth refinement
Publishing
Showcase manager
Curate which items shape the public story and how they are ordered across the portfolio.
Toggles visibility
Controls display order
Bridges raw platform content to public pages
Monitoring
Sync logs
Operational visibility is essential when the site depends on external platforms and scheduled data movement.
Review failures quickly
Understand recent sync behavior
Base for future incident handling
Route flow
How this module moves from concept to public output
Phase 01
Connect providers
Store credentials and configuration for supported platforms.
Phase 02
Sync and normalize
Convert raw provider responses into shared internal records.
Phase 03
Curate and publish
Promote approved content through public endpoints and route pages.