Yodo Imports
Website and content workflow
An import company had a slow website and no simple way for leadership to review content before it went live. I built a faster website and a clearer way to review and publish updates.
The problem
The existing site was slow, difficult to maintain, and separated from the way the client actually needed to review trust-sensitive sourcing content. Updating it depended on a fragile visual editing workflow.
What I built
I designed the page as semantic HTML and CSS, then compiled validated sections into Carbon Fields blocks. The custom theme keeps the editorial structure maintainable instead of locking the design inside page-builder markup.
Engineering decisions
The design source remains inspectable HTML. A parser validates sections before generating PHP blocks, contrast is checked as part of the design, and WP-CLI handles deployment without manual admin data entry.
What shipped
The live WordPress site and the repeatable section-to-block workflow are the public result. The review hub was part of the source path; its current deployed state should be checked against the client build rather than inferred from an older plan.
Current boundary
The project history shows why source parity, deployment boundaries, and content claims need to be checked together. This page shows the build method, not a blanket performance or commercial claim.
See one build move from design source to WordPress workflow.
The first phase made the design inspectable. The second phase carried that structure into a maintainable WordPress theme and an editorial review path.
From design source to WordPress workflow
Two implementation phases share one goal: make the content easier to understand, review, and maintain.
Design source
The first phase separated the content and trust story from a page-builder canvas. The design could be reviewed as semantic HTML and CSS, then carried into the WordPress implementation without losing the original structure.
<section aria-labelledby="trust-heading">
<h2 id="trust-heading">How the buying process works</h2>
<ol>
<li>Explain the verification step.</li>
<li>Show what the buyer receives.</li>
</ol>
</section>The design source and the WordPress port are shown as related phases, not as unrelated projects.
The client can keep the content structure while the implementation remains maintainable.
The live WordPress site is the client-facing system; this page explains the build, not an unverified performance promise.
Client content, private deployment details, and broad commercial claims are intentionally omitted. The live site is the public artifact.