Write for Nadhebe: Contributor Guidelines

What We Publish

Nadhebe publishes practical, high-value technical content aimed at developers building with modern AI tools, open-weights models, and software infrastructure. Topics of primary interest include:

• Agentic Frameworks & Protocols: Model Context Protocol (MCP) server implementations, tool-calling architectures, and agentic workflows.
• Local Model Serving & Inference: Running and quantizing open-weights models locally with Ollama, vLLM, SGLang, and consumer GPU setups.
• Developer Tooling & Workflows: CLI tools (such as Claude Code and Gemini CLI), AI-assisted IDEs, and automation pipelines.
• Practical API Integrations: Real-world integration tutorials for Anthropic Claude, OpenAI, Google Gemini, and open-source AI APIs.
• Client-Side Utilities: Creative applications of browser-native web APIs, WebAssembly, and privacy-respecting client tools.

Content Quality Requirements

To maintain high technical standards for our readers, all submissions must satisfy the following criteria:

• Originality: Submissions must be original work written by you. We do not accept AI-generated filler, spun articles, or content syndicated from other publications without explicit permission.
• Reproducible Code: Every tutorial must include complete, functional code examples tested against current software versions. Readers should be able to follow your steps and achieve the exact same outcome.
• Prerequisites & Environment: Clearly state required dependencies, software versions (Node.js, Python, OS), and API credentials at the start of your article.
• No Promotional Spin: Articles should focus on solving technical problems. We do not publish promotional advertorials or product pitches disguised as tutorials.

Formatting & Structure

• Format: Submissions should be provided in clean GitHub Flavored Markdown (`.md`).
• Headings: Use clear, logical heading hierarchy (`##` for main sections, `###` for sub-steps).
• Code Blocks: Specify the language identifier on all fenced code blocks (e.g., ```` ```typescript ````, ```` ```python ````, ```` ```bash ````).
• Images & Diagrams: Include descriptive alt text for all screenshots, architecture diagrams, or flowcharts.

How to Pitch an Article

Before writing a complete draft, we strongly recommend sending an outline or pitch to our editorial desk:

1. Working Title: A clear, descriptive headline for your proposed article.
2. Target Audience: Who the article is for (e.g., frontend engineers, backend developers, ML practitioners).
3. Outline: 3–5 bullet points outlining the core sections, code examples, and key takeaways.
4. Your Background: A brief sentence about your background and experience with the topic.