Skip to content

Guest posts

Write for Us: SaaS, Coding, Development and AI Guest Posts

WebTransport Day is an independent resource for web developers building realtime apps and SaaS products. If you build with code and can show how, send us a pitch.

Pitch an article Read the guidelines

What topics do we accept for guest posts?

We cover the web platform, realtime apps and the tools developers use to build them. These are the four areas open to guest authors.

SaaS

Building and running a SaaS product from the developer’s seat.

  • Multi-tenant architecture and data isolation
  • Realtime features: live dashboards, presence and notifications
  • Observability, deployment and incident write-ups
  • API design and integrations that held up in production

Coding

Coding posts with code that runs.

  • Language and framework techniques with a working repository
  • Debugging case studies: symptom, cause, fix
  • Code review, refactoring and testing practice
  • Performance work with the method and measurements shown

Development

Web development on the platform as it ships today.

  • Browser APIs: WebTransport, WebSocket, WebRTC and Server-Sent Events
  • CI/CD, serverless and edge deployment
  • Security and reliability for web apps
  • Developer tooling and workflow

AI

AI in the developer workflow, described from real use.

  • AI coding assistants and agents: the task you ran and what failed
  • Adding AI features to a SaaS product
  • MCP and tool integration
  • Prompting and evaluation methods you applied

Have an idea outside this list that helps a developer build a realtime or SaaS app? Pitch it and choose “Something else” as the topic.

What makes a good guest post?

  • Original and unpublished

    Not posted elsewhere and not a rewrite of someone else’s article.

  • First-hand

    Say what you built, tested or shipped, and what went wrong. If you did not run it, do not report an outcome.

  • Sourced

    Link specifications, documentation and repositories for technical claims. State versions and dates.

  • Runnable

    Code works as printed, in fenced code blocks with the language named.

  • Specific

    A narrow problem answered fully beats a broad overview.

  • Disclosed

    Say so if you work on, or have a stake in, a tool you write about.

Our standards for facts and testing are set out in the editorial policy. Guest posts follow the same rules as everything else here.

What guest posts do we not publish?

  • Promotional posts about one product, company or service.
  • Articles already live elsewhere, or reworded from another source.
  • Unedited AI-generated text. AI tools are fine for drafting; you stay responsible for every claim and every line of code.
  • Benchmarks, rankings or comparisons without the method behind them.
  • Posts written mainly to place links.

What are the guest post submission guidelines?

Length
About 1,200 to 2,500 words.
Structure
Question-style H2 headings, short paragraphs, and a table where you compare things.
Opening
A direct answer of 40 to 60 words at the top, as our own guides have.
Code
Fenced code blocks with the language named. State the versions you used.
Sources
Link primary sources: specifications, official documentation and repositories. List them at the end.
Images
Original screenshots or diagrams with alt text. No stock images.
Links
Links go to primary sources and relevant documentation. Promotional links are removed in editing. Your author note may carry one link to your site or profile.
Author note
Up to 50 words: who you are and what you work on.
Draft
Send the outline first. Write the full post once we agree the angle, as Markdown or a shared document.
Editing
We edit for accuracy, clarity, length and house style, and may ask you to verify claims. We decide what to publish and when.

How does guest posting work?

  1. Step 1

    Pitch

    Send the form below with a working title and an outline.

  2. Step 2

    Review

    We read it against the topics and guidelines on this page. If it fits, we reply by email to agree the angle.

  3. Step 3

    Draft

    You write the post. We check technical claims and send edits.

  4. Step 4

    Publish

    We publish it with your name and author note.

Pitch your guest post

Tell us who the post is for, what you built or tested, and what the reader can do afterwards. A clear outline helps us answer quickly.

Prefer email? Write to contact@webtransport.day.

Your site, GitHub or LinkedIn.

The closest fit for your idea.

Who it is for, what you built or tested, what the reader can do afterwards, and the main sections.

Up to three links to articles, docs or repositories you wrote. One per line.

Required. We use what you send only to reply. See the privacy page.

Guest post FAQ

Which topics do you accept guest posts on?

SaaS, coding, development and AI, with a focus on web developers building realtime apps. That includes WebTransport, WebSocket and other realtime protocols, AI coding tools, SaaS architecture and the tooling around them.

Can I mention or link to my own SaaS product?

Yes, where it is relevant to the topic and you disclose your connection. The post has to teach something that works without your product, and promotional links are removed in editing. Your author note can link to your site.

Can I use AI tools to write my guest post?

You can use AI tools to research and draft. You must verify every claim, run every code sample and rewrite the text in your own words. We do not publish unedited AI-generated text.

Can I republish a post that is already on my blog?

No. We publish original work that has not appeared elsewhere. If your existing post suggests a new angle, pitch that instead.

What happens after I submit the form?

Your pitch is emailed to our editors. If the angle fits our topics, we reply to agree an outline. We may not be able to reply to every pitch, so please do not send the same one twice.

Do you edit guest posts?

Yes. Every accepted post is edited for accuracy, clarity and length, and its technical claims are checked against sources before publication.

Where do I send questions that are not a pitch?

Use the contact page. It also covers corrections to published pages.

Before you pitch, read our guides, the AI coding section and the editorial policy. For anything that is not a pitch, use the contact page.

Type to search. Esc closes.