Guest posts Open pitches
We publish practical engineering writing about WordPress, Astro, and Laravel, and about the products we build on them. Send a short outline rather than a finished draft, and we will tell you quickly whether it is a fit.
Our readers build and maintain WordPress sites, ship Astro front ends on Cloudflare, and run Laravel applications behind them. They come for specifics they can apply the same week. A post that explains how you solved a real problem, with the code and the trade-offs, will land far better than a survey of a topic anyone can search.
What we publish
This is the stack we ship with every day, so we can tell whether a claim holds. Writing outside it is not a fit for this blog, however good it is.
01
Plugin and theme architecture, the REST API, WP-CLI, performance work on large sites, database and query tuning, security hardening, and the realities of shipping to sites you do not control.
Written for people who maintain WordPress, not for people choosing it.
02
Astro 6 with Tailwind v4, static and hybrid rendering, Cloudflare Workers, edge caching and invalidation, headless WordPress feeding an Astro front end, and migrating a page tree without losing URLs.
The stack this site runs on, so we can check what you claim.
03
Laravel 11, testing with Pest, queues and scheduling, billing and subscription flows, multi-tenant SaaS design, and the seams between a WordPress front end and a Laravel service behind it.
Application engineering, not framework tourism.
Name the reader and the problem in the first line. Show the outline as headings so we can see the shape. Say what the reader will be able to do afterwards. Include a link to something you have written before, even if it is a README or an internal doc you can share. We care more about whether you have done the work than about your byline.
Anything already published elsewhere. Product roundups written to place a link. Posts about tools we do not use, which we cannot check. Generic advice with no code, no numbers, and no specifics. Pitches that open with link requirements or offer payment for placement. Text that reads as machine-generated filler.
Email shashank@wbcomdesigns.com with your working title, an outline as headings, and a line on who the reader is. Keep the subject line starting with "Guest post pitch" so it reaches the right place. If the topic fits, we will come back with edits to the outline before you write the draft.
We read every pitch that is on topic and reply either way. If it is a fit, we agree the outline first, then you write. Once the draft is in, we edit for house style and accuracy, send anything substantive back to you, and publish with your byline and author bio.
Before you pitch
Web development on WordPress, Astro, or Laravel, or on the stack we ship with: PHP 8.2, Tailwind v4, Cloudflare Workers, GitHub Actions. Writing about the kinds of products we build also fits: community platforms, membership and LMS sites, marketplaces, job boards, and directories. If your topic sits outside that, it is not a fit for this blog however good the writing is.
Pitch first. Send a working title, a short outline, and one or two sentences on who the reader is and what they can do after reading. A finished draft on the wrong topic wastes your time more than ours.
Yes. It must not be published anywhere else, including your own blog, Medium, or LinkedIn, and it must not be republished after we run it. We do not accept spun, translated, or AI-generated filler.
One link in the author bio, and in-text links only where they genuinely help the reader. We do not accept paid links, affiliate links, or link-insertion requests on existing posts, and we do not sell placements. Pitches that lead with link requirements are declined.
Yes. We edit for house style, accuracy, and clarity, and we may retitle. Anything that changes your technical meaning goes back to you before it publishes.
No. This is not a paid placement programme in either direction. You keep the byline, the author bio, and the link to your site.
Have a topic in mind?
A working title, an outline as headings, and a line on who the reader is. That is enough for us to say yes or no.
WBComDesigns is amazing. The WP plugins and themes are of top notch quality with lots of features and updated very frequently. Supports are very responsive and helpful. I use Reign with TutorLMS, and the experience is surprisingly smooth.…