Asymmetric Website — WordPress Template Decision

Decision

On 2026-04-01, the team decided to direct designer Mikal to build the Asymmetric website using a WordPress template rather than pursuing a custom JavaScript build.

Context

The Asymmetric website build had stalled. Mikal had paused work due to competing priorities (Cordwainer, other Asymmetric tasks) and had begun exploring a custom JavaScript approach alongside a "David vs. Goliath" visual theme. This introduced two risks:

1. Scope creep / delay — A custom JS build trades one set of technical problems for another (per internal developer feedback), with no clear speed advantage.
2. Failed experiment risk — If the custom approach didn't work out, the team would need to revert, losing additional time.

The Asymmetric launch was already blocked on multiple fronts (LinkedIn Ad graphics, gated guides), making a predictable website delivery timeline critical.

Decision Rationale

• WordPress is a proven, stable standard that the team knows how to build and maintain.
• Internal developers (Eshock and Jeff) both noted that JavaScript builds carry equivalent or greater complexity than WordPress — not a meaningful upgrade.
• A WordPress template allows the site to launch faster and be iterated on later.
• The custom design / branding can be applied in a future phase once the launch is complete.

"What if we totally go this crazy way, and then it doesn't work, and then we end up having to go back?" — Karly Oykhman

Action Taken

• Melissa Cusumano was assigned to communicate the decision to Mikal and redirect him to a WordPress template.
• The "David vs. Goliath" theme was deprioritized as the primary visual concept for the site.
• A future custom design pass remains on the table once the initial site is live.

Broader Pattern

This decision reflects a recurring principle in client website work: avoid experimental builds when a launch deadline is active. Custom or non-standard builds are better suited to greenfield projects with flexible timelines, not launches already blocked by other dependencies.

See also: ^[1] | ^[2]