Translation AI workflow
Click to enlarge
Workflow evidence for source assets, orchestration, QA gates, reviewed output, and archive evidence.
Builder Log 001
Turning pl8ypus into an AI builder site.
Published / Foundation
May 2026
This first builder log marks the point where pl8ypus stopped being a loose portfolio idea and became a focused AI builder site. The purpose is simple: show serious, practical AI systems for marketing operations through visible architecture, controlled build decisions, and proof-led progress.
Visual evidence added
The first build entry now includes the visual proof layer added to the site: workflow imagery, dashboard imagery, and architecture evidence panels that can be opened in a lightbox for closer review.
Marketing Intelligence dashboard
Click to enlarge
Dashboard evidence for ads, social, web, campaigns, and executive AI readouts.
AI delivery evidence
Click to enlarge
Architecture evidence for route selection, review, audit, rollback, and validation controls.
What changed
- Repositioned pl8ypus around governed AI systems for marketing operations
- Created a flat static site structure for fast iteration and simple deployment
- Built dedicated pages for Translation AI and Marketing Intelligence AI
- Added speaking, about, and builder log pages
- Added a Formspree contact modal for demos, speaking, collaboration, and build discussions
- Moved from Tailwind CDN to compiled local CSS so deployment is stable
- Standardised the top navigation and build dropdown across the site
- Added visual evidence panels for Translation AI, Marketing Intelligence AI, and AI delivery controls
- Added image lightbox previews so architecture and workflow evidence can be inspected
- Connected the homepage and build pages through a shared visual evidence language
What this proves
- The model is not the product — the workflow around the model matters
- AI builder credibility needs architecture, controls, evidence, and demos
- Static HTML, Tailwind, and vanilla JavaScript are enough for a credible front-end when the system architecture is clear
- Senior stakeholders need to see governance, review states, rollback paths, and delivery discipline early
- Visual evidence makes the build more credible than copy alone
- Senior stakeholders need to inspect the workflow and control layer, not just read about it
What comes next
- Replace illustrative panels with real screenshots as the demos mature
- Build the first upload-to-translation demo workflow
- Capture the first real Marketing Intelligence AI dashboard state
- Prepare Builder Log 002 once the next build step is complete
Current status
Homepage: evidence added
Build pages: visual proof added
Images: lightbox enabled
CSS build: stable
Next: demo workflow
Log entry
001 / Foundation