Content

The process we follow to write content and the channels we publish it to.

Channels

Directory of public channels we post content on.

Process

Each content piece follows a process from idea to publication. This section outlines the processes for different content types.

Articles

An overview of our article writing process and how we ensure effective content production at Wednesday.

Articles are detailed, longer, and show thought leadership. Each article should be between 3500 to 4000 words in length.

Article Structure

Every article at Wednesday follows a defined structure. Get an overview of the various sections to cover in each article here.

Each section in an article has one or more section types.

• Introduction: Hook the reader, introduce the topic briefly, and tell the reader what they'll build and what they'll learn.

The introduction should be short, and should answer the following 5 questions:

1. What is your topic?
2. Why is it important to learn?
3. What will the reader build in this article?
4. What will the reader learn in this article?
5. What are the prerequisites? (if any)

While doing so, remember to hook the reader and get them excited.

• Instruction Sections: Provide the step-by-step instructions for adding code or building the app, and (where possible) end with a "build & run" step and screenshot.
  1. Include every step: for example if you create a new file say select file → new
  2. Build and run: Always include a screenshot after a build and run step.
• Getting Started Section: The first instruction section in an article is a special case.

It should always be named Getting Started and should cover the initial steps to get started with the rest of the article. If you have a starter project, this section should contain:

1. Instructions to download the starter project
2. An overview of the starter project: build and run with screenshots, and optionally an overview of the code.
3. An overview of the problem: what feature(s) you are trying to add.

• Theory Sections: Explain high-level theory that you need to understand before you dive into the code, usually without step-by-step instructions.
  • Explain just in time: Don't overcomplicate by spending too much time in theory.
  • Explain complicated material: The more complicated the more theory.
  • Use images and illustrations: Get in touch with Ali to get custom illustrations.
• Reference Sections: Lists what options are available for an API / technology for future reference; even those outside of the scope of the tutorial itself.

Choose the most useful operations to cover, then add a short reference section to show the reader what other operations are available.

• Where to Go From Here?: The final section — summarizes what the reader has learned, and where they could go for more information.
  • First-line = download: "You can download the completed project files by clicking on the Download Materials button at the top or bottom of the article."
  • Summary [Optional]: Brief summary of what you covered.
  • 1-3 paragraphs of resources: List resources for readers who want to learn more.

These sections can be composed in any order (except for the Introduction and Where to Go From Here sections which are always first and last).

The Process

Choose your Topic

Write an outline

Sample Project

First Draft

Polish your Draft

The Board

We maintain a board with swimlanes and a calendar on Notion. Access to this workspace will be given to all writers.