MediaBridge

Publishing platform that pushes business content across a network of 101 media sites.

Visit the product

101

active media sites

MediaBridge dashboard count

1,557,208

publication records

Dashboard count. Not unique articles, indexed pages or traffic.

In short

I lead the product family built around BridgeBooks, a Japanese subscription product. MediaBridge is the Laravel and Filament application that receives BridgeBooks customer information and manages publication across a network of media and directory sites. I built the receiving sites, the WordPress integration plugin, and three supporting products: AIO-CDN, an AI website builder, and Open To AI.

Who it is for

BridgeBooks subscribers whose business information is published across the media network, and the operators who manage those publications from the MediaBridge dashboard.

The problem

BridgeBooks customers need their business information published and kept current across a large network of media sites. Without one system in the middle, every site is configured and updated separately, and there is no single place to see what has been published.

What I delivered

Built MediaBridge in Laravel with a Filament dashboard: it receives BridgeBooks customer information and manages publication across the site network.
Built and maintain the receiving media sites, each a React frontend on a WordPress backend.
Developed the WordPress integration plugin that connects each site in the network back to MediaBridge.
Proposed AIO-CDN, took the concept through stakeholder acceptance, and built it: it generates supporting website content and assets including FAQs, structured data, robots files, llms.txt and llms-full.txt.
Built the AI-assisted website builder, which generates a site from business information, Google Business Profile data, reviews and social posts.
Built Open To AI, a tool that assesses a site against supported SEO and AEO implementation criteria.
Worked across the AWS footprint for this product family: RDS, ECS, EC2, load balancing and Terraform.

Architecture

How the pieces fit together, from the client down to data and external services.

System topology

Engineering challenges

One publication, many sites
Each receiving site runs a React frontend on a WordPress backend. Rather than configuring publication per site, I built a WordPress integration plugin so the network can grow without the publishing path changing.
Taking AIO-CDN from idea to product
I proposed the concept, presented it to stakeholders and received acceptance to build it. It generates the supporting assets a site needs to be readable by search engines and AI systems: FAQs, structured data, robots files, llms.txt and llms-full.txt.
Measuring implementation, not outcomes
Open To AI scores a site against supported SEO and AEO implementation criteria. It reports what is implemented. It is not a ranking, traffic or AI recommendation measure, and I do not present it as one.

Outcome

MediaBridge runs in production. Its dashboard reports 1,557,208 publication records across 101 active media sites. I started the work independently and now have one maintainer supporting smaller tasks. AIO-CDN and the website builder are approaching release and sit behind login.

Over 1.55 million publication records across 101 active media sites
Laravel and Filament platform plus a custom WordPress integration plugin
Proposed AIO-CDN and carried it from concept to implementation
Four products in one family: MediaBridge, the media sites, AIO-CDN and Open To AI

References

Product pages and store listings for this work. They show the product, not a breakdown of who built which part.