CyberV
Corporate site for a regional tech consulting firm. Laravel back end, Tailwind front, full bilingual content model, halved page weight against the previous WordPress build.
About the project.
CyberV is a regional technology consulting firm that needed a corporate site they could update themselves without calling a developer for every line edit. I built a Laravel back end with a bilingual content model, a Tailwind front, and an editor experience that lets non-technical staff publish in Arabic and English from the same form. The previous WordPress build was heavy and slow on Gulf mobile networks; the new site loads in under a second on 4G.
What changed.
from kickoff to launch
increase in qualified leads
What we walked into.
A regional tech-consulting firm needed a corporate site they could update without calling a developer for every line edit — bilingual ar/en, fast on Gulf mobile networks, brand-aligned with their evolving identity.
What we did.
Laravel back end with a bilingual content model, Tailwind front, an editor experience where non-technical staff publish ar/en from the same form. Replaced a slow WordPress build that struggled on 4G.
What it became.
Page weight halved. Sub-second 4G load. Bilingual editing flow the team uses without engineering support.
My role on this project.
Solo · 100% — design, Laravel back end, Tailwind front, bilingual content model, deployment. CyberV staff supplied brand direction and content; everything technical (and most of the visual implementation) is mine.
Designer + brand implementer
Translated CyberV brand identity into web. Bilingual typography pass (Arabic + Latin). Tailwind config + design tokens.
Backend engineer (Laravel)
Bilingual Eloquent model (translatable fields via Spatie/translatable), Filament admin for non-technical editing, lead form pipeline.
Front-end engineer
Tailwind + Alpine.js. Hand-tuned for 4G performance. Lazy-loaded media, lighthouse 90+.
DevOps
Cloudways VPS, daily Forge-managed backups, custom domain, TLS auto-renewal.
The numbers that matter.
- 50%Page weight reductionVersus the previous WordPress build — confirmed via Chrome DevTools network panel before/after.
- <1s4G load time · p75Saudi 4G network simulated; verified on a real Gulf-region device.
- 90+Lighthouse perf scoreOn the home + services pages. Other templates 85+.
- Bilingualar/en single formEditors write both languages in one Filament form — no separate posts.
- 0Plugin dependenciesNo WordPress plugin sprawl. All features are first-party Laravel code.
What was actually broken.
CyberV had grown past what their WordPress site could honestly represent. The site was slow on the very network their target clients use (Gulf mobile), the bilingual experience required two separate posts per page (with no enforcement they stayed in sync), and every meaningful change required a developer because the page builder did not support their brand patterns. The brief: a site they can edit themselves, that loads instantly on a 4G phone in Riyadh, that reads as serious in both Arabic and English.
The hard surface area.
- 01Bilingual content model that enforces ar/en parity without doubling the editing surface area.
- 02Performance budget that survives Saudi mobile networks (highly variable latency, occasional 3G fallback).
- 03Editor experience that an account manager — not a developer — can use comfortably.
- 04Brand-aligned but flexible visual system that survives 2-3 brand refreshes per year without engineering touch.
Engineering wins worth naming.
Single-form bilingual editing
Filament resource with paired ar/en fields side by side. Validation requires both languages before save. Empty state shows "translation missing" badges in the admin index, not just on the live site.
Page weight discipline
Self-hosted fonts (subset + WOFF2 only), no JS framework, lazy-loaded images with `loading="lazy"` + `decoding="async"`, Tailwind's purge cuts CSS to <12KB gzipped.
How the system is wired.
Edge tier
Application tier
Data tier
The decisions behind each choice.
Laravel + Filament
- Filament admin is the fastest way to build a non-technical editor experience in PHP. Out of the box: tables, forms, validation, file uploads — all the boring parts.
- Laravel + Spatie/translatable gives bilingual content without two posts per page.
- Same stack the client's next vendor (if any) can pick up — no exotic dependencies.
Tailwind + Alpine over React
- A corporate site is mostly text + images. React would have shipped 50KB+ of runtime for zero functional benefit.
- Alpine handles the small interactive bits (mobile nav, modal) in 8KB.
What the build taught us.
- Page weight is not a vanity metric in the Gulf. 4G coverage is excellent but inconsistent — every saved KB shows up in bounce rate.
- Editor experience determines update frequency. If the admin is awkward, the site goes stale within a year.