My Portfolio Runs on Cloudflare Pages. Client Sites Run on WordPress + Elementor. Here's Why Both Are Right.

I build full-custom WordPress + Elementor sites for clients. My own portfolio runs on Cloudflare Pages. Those two facts are not a contradiction — they are exactly how a developer who understands the stack is supposed to operate.

The Honest Reason Most Developers Stay on One Platform

WordPress powers 43 percent of the web (W3Techs, 2026). Most developers default to it for everything — their own site, client sites, side projects — because it is familiar, not because it is always right. I do the opposite: I use the platform that fits the use case, and I am direct about which one that is.

For my own portfolio, Cloudflare Pages is the correct call. For your business site, full-custom WordPress + Elementor is the correct call. The reasoning behind both decisions is what you should hear before we talk about working together.

Why My Portfolio Runs on Cloudflare Pages

My site has one editor: me. I push to Git. I do not need a CMS. I do not need a client to update a headline on a Tuesday afternoon without touching code.

What I do need is a site that performs flawlessly and proves I can build on the edge. Here is what the Cloudflare stack delivers:

Edge delivery at scale. Cloudflare Pages runs across 330+ cities in 125+ countries. My HTML is served from the node closest to the visitor — no origin server round-trip, no PHP execution, no database query on page load. My PSI mobile score is 90+. That is not optimization heroics. That is the architecture doing its job.

Near-zero attack surface. There is no wp-login.php. No xmlrpc.php. No plugin CVE database to monitor. The only dynamic surface on my site is a contact form backed by a Cloudflare Worker — a JavaScript function running at the edge, writing submissions to D1 (Cloudflare's edge SQLite database, free up to 5 million row reads per day) and triggering a Resend email in near-instant time. The WAF wraps all of it.

Marginal infrastructure cost. Workers are $5/month for 10 million requests. Pages is free. D1 is free at my volume. Running my personal portfolio on this stack costs me almost nothing, which is appropriate — it is a portfolio, not a product.

The point of running my own site on Cloudflare is not to avoid WordPress. It is to demonstrate that I can build edge-native. That is a different credential — and it makes me a better WordPress developer because I understand the tradeoffs from both sides.

Why I Build Client Sites on Full-Custom WordPress + Elementor

Your situation is different from mine. You have a team, or you will have one. Someone who is not a developer needs to publish a blog post, update a service description, swap a team photo, or spin up a landing page for a campaign — without calling me. WordPress + Elementor is built for exactly that.

You Own the CMS, Not Just the Site

WordPress is the most widely understood CMS on the planet. Your next hire knows it. Your marketing agency knows it. The freelancer you bring in for a one-off project knows it. When I hand over a full-custom WordPress + Elementor build, I am handing you an asset you can manage, extend, and staff around — not a bespoke system that only I can touch.

The Plugin Ecosystem Is a Legitimate Business Asset

WooCommerce, Yoast SEO, WPForms, MemberPress, Advanced Custom Fields, Gravity Forms — these are mature, production-tested tools with dedicated support and update cycles. Building equivalent functionality from scratch on any other stack would cost multiples of the WordPress implementation. I do not fight the ecosystem. I use it deliberately.

Elementor Gives Your Team Visual Editing Without Breaking the Design

Full-custom Elementor builds are not template sites. I build from the kit up — global colors, global fonts, custom widget presets — so the design system is locked in at the theme level. Your team edits content inside that system. They cannot accidentally break the visual hierarchy because the constraints are structural, not just stylistic.

Content Workflows Belong in a CMS

If you are publishing case studies, service pages, and blog content regularly, you need a proper content workflow — drafts, revisions, scheduled publish, role-based access, media management. WordPress has had this for 20 years. It is not a workaround. It is the product.

What "Full-Custom" Actually Means

I do not install a $79 theme and hand you a site. A full-custom WordPress + Elementor build from me means:

• Kit-level design system — every global color, font, button style, and heading preset defined once, applied everywhere
• Custom page templates — built to your content types, not shoehorned into a generic layout
• Plugin selection with intent — every plugin has a job; nothing is installed "just in case"
• Performance baseline — hosting configuration, caching layer, image optimization, and Core Web Vitals review before handoff
• Documented handoff — you get a short-form guide to the things your team will actually edit

The Two-Platform Stance Is the Credibility Piece

A developer who only knows one stack is a hammer looking for nails. I built my own site on Cloudflare Pages because that was the right tool. I build client sites on WordPress + Elementor because that is the right tool for clients. Knowing why each platform wins in its lane — and being willing to say so publicly — is how you avoid paying for the wrong architecture.

If you come to me and your project is genuinely better served by a different approach, I will tell you that before we scope a single page. That directness has never cost me a client relationship. It has earned several.

Working With Me

I scope projects before I build them. That means one honest conversation about what you actually need, what your team will edit, and what the site has to do in two years — before I write a line of code.

See how I work with clients for a plain-English breakdown of the full-custom WordPress + Elementor stack and process.

Ready to talk through your site? Book a 30-minute call.