CADE Media Integration & Author Profiles for Spatial AI — June 29, 2026

Today, I set out to enhance the CADE media integration and author profiles on my spatial AI platform, aiming to create a more cohesive user experience for both creators and consumers. After a grueling 22-hour coding marathon, I successfully shipped 38 commits that included crucial features like a public image route for CADE media and multi-tenant awareness for the WordPress emulation. It was a long day filled with both triumphs and trials, but I’m proud of the progress made.

One of the standout features I implemented was the new public image route at /api/files/cade-media/[name]. Previously, the single-segment route didn’t account for the cade-media subpath, leading to 404 errors for uploaded media and author headshots. By addressing this, I ensured that the author photos, like Robert Bibb’s LinkedIn headshot, are now accessible and displayed correctly. It’s a small but significant user-facing improvement that contributes to a professional appearance on author profiles.

Additionally, I revamped the author profile pages to include a dedicated section at /profiles/[slug] and an archive at /profiles. This not only renders the author’s name, headline, bio, and social links but also injects structured Person/ProfilePage JSON-LD for better SEO visibility. One of the goals here was to ensure that these pages are easily discoverable by Google and other AI systems, so I included a hidden discovery signature within each profile. This should help boost the visibility of our authors in search results, aligning perfectly with my ambition for the platform.

The multi-tenant foundation for CADE was another major milestone. I made the /wp-json/* API domain-aware, allowing it to resolve the tenant from the host. This means that each tenant can have their own unique credentials and storage, which is crucial for scaling the platform. I also provisioned a one-click setup for CADE, where users can enable CADE for their sites and receive their site URL and credentials. This makes onboarding significantly easier and more intuitive for new users.

However, it wasn’t all smooth sailing. I faced a few bugs that consumed a considerable amount of time. For instance, the CADE schema verification process initially failed due to a mismatch in the expected contract with the existing cade-seo plugin. I had to meticulously debug the GET and PUT requests to ensure that they returned the correct schema data. This involved a lot of trial and error, including logging the exact sequence of operations to confirm what was being sent and received. Ultimately, I had to adjust the API to echo back the raw payload to ensure that the verification process would not flag it as 'Not Verified'. It was a frustrating but educational experience that underscored the importance of aligning with existing contracts when working with plugins.

In the spirit of building a one-man-show company aimed at a billion-dollar valuation, I also reflected on how I managed to tackle these complex features mostly solo, leveraging Claude Code in VS Code instead of paying for additional tools. It’s a testament to what can be achieved with the right mindset and resources at hand. The cumulative work on CADE not only enhances the platform but also positions it as a competitive player in the agentic web space. Each feature I implement brings me one step closer to realizing my vision of a fully integrated spatial AI ecosystem that empowers creators and users alike.

As I wrap up today’s entry, I’m reminded of the relentless grind that comes with building something great. Each commit, each debug session, each late-night coding spree adds up to a larger picture. I’m excited about what’s to come, especially as I continue to refine the CADE functionalities and expand the capabilities of the platform. Tomorrow promises to bring new challenges, but I’m ready to face them head-on, fueled by the progress made today.