We publish practical, accurate and original writing about building with AI. There are two ways to contribute: guest articles and sponsored placements.
Anyone who has something useful to teach. Our contributors include working engineers, researchers, ML practitioners, product builders, and technical writers at all levels of experience. First-time writers are welcome — our editorial process is designed to help you publish your best work.
Note: We do not accept submissions on behalf of unnamed authors. If a company wants to contribute, the named author should be the person who actually wrote the article and is willing to be credited.
Step-by-step guides that walk a reader through completing a specific task. Must include prerequisites, numbered steps, expected results, and an honest account of limitations.
Long-form articles that go beyond the documentation to explain how something works, why it was designed that way, and when to use it or avoid it.
What you or your team learned from a specific project — including what failed and why. Must focus on transferable lessons, not just a success story.
A well-reasoned position on a technical or industry topic, supported by evidence and your own experience. We publish counterintuitive and critical perspectives.
We do not publish: press releases, product reviews by the product's maker without disclosure, content that is primarily a list of links, or articles whose main purpose is to drive traffic to a commercial property.
Educational, non-promotional content. You share your expertise; Ploba provides editorial support, a byline, and distribution. No fee to submit or publish.
A paid placement for companies that want to reach our audience. Same editorial review as any other submission, labelled “Sponsored” prominently.
Full link rules and editorial standards are in our publishing policy.
Name the specific audience and their starting level. “Engineers who have used the OpenAI API but have not yet moved to production” is more useful than “developers interested in AI”.
State the concrete takeaway. Prefer “they will be able to implement streaming responses with proper error handling” over “they will learn about X”.
Briefly describe your relevant experience. Include links to past writing if you have it — a technical blog post, documentation you wrote, or a GitHub profile works fine.
Your main section headings with a sentence or two on what each section covers. 200–300 words is enough. A Google Docs link is welcome but not required.
An editor works with you to strengthen the article. Specific, actionable feedback — not generic requests to “improve quality”.
Published articles carry your name, a short bio, and one link to a site of your choice.
We share published articles across our channels to our community of AI developers and practitioners.
We tell you quickly if a pitch is not right for us. If we can see a way to make it work, we will say so.
Start with a short outline. We’ll get back to you with feedback within a few working days. Read the writing guidelines first.