CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" /> <meta property="og:title" content="Slack" /> <meta property="og:type" content="website" /> <meta property="og:url" content="/slack/" /> <meta property="og:site_name" content="Write the Docs" /> <meta property="og:description" content="Thanks for your interest in our Slack network. We have over 22,500 people who have joined, and you can be one of them. Our Slack network has lots of people hanging out and chatting about documentat..." /> <meta property="og:image" content="https://www.writethedocs.org/_static/logo-opengraph.png" /> <meta property="og:image:alt" content="Write the Docs" /> <meta name="description" content="Thanks for your interest in our Slack network. We have over 22,500 people who have joined, and you can be one of them. Our Slack network has lots of people hanging out and chatting about documentat..." /> <meta name="twitter:card" content="summary_large_image" /> <title>Slack — Write the Docs</title> <link rel="stylesheet" type="text/css" href="../_static/pygments.css" /> <link rel="stylesheet" type="text/css" href="../_static/alabaster.css" /> <link rel="stylesheet" type="text/css" href="../_static/css/global-customizations.css" /> <link rel="stylesheet" type="text/css" href="../_static/css/survey.css" /> <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script> <script src="../_static/jquery.js"></script> <script src="../_static/underscore.js"></script> <script src="../_static/_sphinx_javascript_frameworks_compat.js"></script> <script src="../_static/doctools.js"></script> <script src="../_static/sphinx_highlight.js"></script> <link rel="canonical" href="https://www.writethedocs.org/slack.html" /> <link rel="shortcut icon" href="../_static/favicon-96x96.png"/> <link rel="index" title="Index" href="../genindex/" /> <link rel="search" title="Search" href="../search/" /> <link rel="next" title="BIPOC Documentarians" href="../bipoc/" /> <link rel="prev" title="Newsletter & Mailing lists" href="../newsletter/" /> <link rel="stylesheet" href="../_static/custom.css" type="text/css" /> <link rel="alternate" type="application/atom+xml" href="../blog/archive/atom.xml" title="Blog" /> <link href="https://netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.min.css" rel="stylesheet" /> <style type="text/css"> ul.ablog-archive { list-style: none; overflow: auto; margin-left: 0px; } ul.ablog-archive li { float: left; margin-right: 5px; font-size: 80%; } ul.postlist a { font-style: italic; } ul.postlist-style-disc { list-style-type: disc; } ul.postlist-style-none { list-style-type: none; } ul.postlist-style-circle { list-style-type: circle; } </style> <script async type="text/javascript" src="/_/static/javascript/readthedocs-addons.js"></script><meta name="readthedocs-project-slug" content="writethedocs-www" /><meta name="readthedocs-version-slug" content="latest" /><meta name="readthedocs-resolver-filename" content="/slack/" /><meta name="readthedocs-http-status" content="200" /></head><body> <div class="document"> <div class="announcement-banner-wrapper"> <div class="announcement-banner"> <p>Portland 2025 speakers announced. <a href='/conf/portland/2025/'>Buy your ticket now</a></p> </div> </div> <div class="documentwrapper"> <div class="bodywrapper"> <div class="body" role="main"> <div class="breadcrumbs"> <a href="../">Home</a> » <a href="../about/stay-connected/">Stay Connected</a> » </div> <section id="slack"> <h1>Slack<a class="headerlink" href="#slack" title="Permalink to this heading">¶</a></h1> <div class="admonition tip"> <p class="admonition-title">Tip</p> <p>Due to an increase in spammers, we now have a short <a class="reference external" href="https://docs.google.com/forms/d/e/1FAIpQLSdq4DWRphVt1qVqH8NsjNnS0Szu_NljjZRUvyYqR7mdc00zKQ/viewform?usp=sf_link">signup form</a> that you must fill out to join our Slack network.</p> </div> <p>Thanks for your interest in our Slack network. We have over 22,500 people who have joined, and you can be one of them.</p> <p>Our Slack network has lots of people hanging out and chatting about documentation. It’s the best way to connect with our community, and to stay in touch with folks you’ve met at our conferences and meetups.</p> <p>Our most active Slack channels are listed below. This should help you get connected to people with similar interests. Please also read the Slack guidelines carefully, and remember that our <a class="reference internal" href="../code-of-conduct/"><span class="doc">Code of Conduct</span></a> also applies to our Slack.</p> <p>If you want to get involved you can:</p> <ul class="simple"> <li><p>Fill out our <a class="reference external" href="https://docs.google.com/forms/d/e/1FAIpQLSdq4DWRphVt1qVqH8NsjNnS0Szu_NljjZRUvyYqR7mdc00zKQ/viewform?usp=sf_link">signup form</a> to join our network.</p></li> <li><p>Feel free to send a Pull Request to update <a class="reference external" href="https://github.com/writethedocs/www/blob/master/docs/slack.rst">this page</a>, if you want to include other channels you enjoy.</p></li> </ul> <div class="admonition note"> <p class="admonition-title">Note</p> <p>Our Slack includes animated emoji, and other animations are sometimes posted. If you think these may be unpleasant for you, you can <a class="reference external" href="https://get.slack.help/hc/en-us/articles/228023907-Manage-animated-images-and-emoji">disable all animations</a> in your Slack client.</p> </div> <section id="slack-history"> <h2>Slack History<a class="headerlink" href="#slack-history" title="Permalink to this heading">¶</a></h2> <p>We don’t pay for our Slack, which means that the community only has access to messages from the last 90 days. That doesn’t mean everything gets lost, though. Here are a few ways to preserve what you’ve learned for yourself and others:</p> <ul class="simple"> <li><p>React to a message with <code class="docutils literal notranslate"><span class="pre">:suggest-for-newsletter:</span></code> emoji to nominate it for inclusion in our next monthly newsletter. Read the newsletter archives at <a class="reference internal" href="../newsletter/"><span class="doc">Newsletter & Mailing lists</span></a> and subscribe if you want them directly in your inbox!</p></li> <li><p>Contribute a summary to one of the Write the Docs site’s <a class="reference internal" href="../about/learning-resources/"><span class="doc">Learning Resources</span></a>.</p></li> <li><p>Turn a discussion into a talk proposal for <a class="reference internal" href="../conf/"><span class="doc">an upcoming Write the Docs conference</span></a>.</p></li> <li><p><a class="reference external" href="https://slack.com/intl/en-gb/help/articles/360042650274-Save-messages-and-files-">Save a message</a> privately in Slack.</p></li> <li><p>Recap what you learned and share it on your own site or social media accounts. Don’t forget to tag <cite>#writethedocs</cite>!</p></li> </ul> <div class="note admonition"> <p class="admonition-title">Why we don’t pay for Slack</p> <p>The Write the Docs Slack community is free to access and we aim to keep it that way. A Slack subscription is prohibitively expensive—over $10,000 per month—for a community as large as ours. Even if we had such resources, upgrading Slack is not a priority and many people feel a freedom in knowing that their words will disappear shortly.</p> </div> </section> <section id="other-chat-platforms-such-as-discord"> <h2>Other chat platforms (such as Discord)<a class="headerlink" href="#other-chat-platforms-such-as-discord" title="Permalink to this heading">¶</a></h2> <p>Write the Docs does not have an official presence on Discord or other chat platforms.</p> <p>People sometimes ask about moving the community to a different tool, like Discord, so we can access more chat history or benefit from fewer chat accounts to manage. We considered that, and decided not to for the following reasons:</p> <ul class="simple"> <li><p>Many workplaces restrict access to social media sites including Discord. Because it’s a work-related community, a lot of people access the Write the Docs Slack from their work computers alongside their employers’ Slack instances. They often cannot do the same for other chat platforms.</p></li> <li><p>Migrating platforms is not a priority for the capacity of our small moderation team. Our community has a <em>lot</em> of people in it - we’ve got over 20,000 registered members. Moving an active community that large to a different platform requires a lot of attention that we believe is better spent on other tasks to serve the community.</p></li> </ul> </section> <section id="autoresponders"> <h2>Autoresponders<a class="headerlink" href="#autoresponders" title="Permalink to this heading">¶</a></h2> <p>We have some helpful Slackbot responses that you can summon in any channel, at any time.</p> <ul class="simple"> <li><p><code class="docutils literal notranslate"><span class="pre">?invite</span></code> / <code class="docutils literal notranslate"><span class="pre">?join</span></code></p> <ul> <li><p>Get a link you can send to a friend to invite them to the Write the Docs Slack. (You can also invite people directly from Slack by clicking <strong>Write the Docs</strong> > <strong>Invite people to Write the Docs</strong>.)</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?conferences</span></code> / <code class="docutils literal notranslate"><span class="pre">?conference</span></code></p> <ul> <li><p>Get information on past and future Write the Docs <a class="reference internal" href="../conf/"><span class="doc">Conferences</span></a>.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?jobseeking</span></code> / <code class="docutils literal notranslate"><span class="pre">?hiring</span></code> / <code class="docutils literal notranslate"><span class="pre">?interview</span></code> / <code class="docutils literal notranslate"><span class="pre">?interviewing</span></code></p> <ul> <li><p>Get information on both hiring and getting hired, including a link to the <a class="reference internal" href="../hiring-guide/"><span class="doc">Guide to Hiring and Getting Hired</span></a>.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?getstarted</span></code> / <code class="docutils literal notranslate"><span class="pre">?resources</span></code> / <code class="docutils literal notranslate"><span class="pre">?learn</span></code></p> <ul> <li><p>We’re always excited to help new people into working on documentation! This is for you if you want some resources on how to get started, including a link to some of our favorite <a class="reference internal" href="../about/learning-resources/"><span class="doc">Learning Resources</span></a>.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?coc</span></code></p> <ul> <li><p>“COC” is short for the <a class="reference internal" href="../code-of-conduct/"><span class="doc">Code of Conduct</span></a>. This is an easy way to get a link to it, and to summon a member of the <a class="reference internal" href="../team/#moderation-team"><span class="std std-ref">moderation team</span></a> if you need one.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?mods</span></code> / <code class="docutils literal notranslate"><span class="pre">?moderators</span></code> / <code class="docutils literal notranslate"><span class="pre">?modsquad</span></code></p> <ul> <li><p>Returns the members of the <a class="reference internal" href="../team/#moderation-team"><span class="std std-ref">moderation team</span></a> if you need to ping someone directly for help.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?history</span></code></p> <ul> <li><p>Returns the answer for one of our most frequently asked questions: why you can’t access the full chat history in the Write the Docs Slack.</p></li> </ul> </li> <li><p><code class="docutils literal notranslate"><span class="pre">?discord</span></code></p> <ul> <li><p>Returns the answer for one of our most common follow-up questions: why we don’t move to a different tool like Discord.</p></li> </ul> </li> </ul> </section> <section id="channel-guide"> <h2>Channel guide<a class="headerlink" href="#channel-guide" title="Permalink to this heading">¶</a></h2> <p>The Write the Docs Slack has _lots_ of channels. Some channels are widely joined, while others are more specialized. Here’s an overview of how we use channels on Slack.</p> <section id="default-channels"> <h3>Default channels<a class="headerlink" href="#default-channels" title="Permalink to this heading">¶</a></h3> <p>Everyone who joins the Slack will be added to these channels:</p> <ul class="simple"> <li><p><strong>#intros</strong> - Introduce yourself! Let people know you’re here, and why you care about docs :)</p></li> <li><p><strong>#announcements</strong> - Community-wide announcements from the Write the Docs organizers.</p></li> <li><p><strong>#general</strong> - The main channel for documentation-related conversation and questions.</p></li> <li><p><strong>#job-posts-only</strong> - Posting jobs. (Talk about your job search in <strong>#work-wanted</strong> and <strong>#career-advice</strong>.)</p></li> <li><p><strong>#wtd-conferences</strong> - Questions and discussion for <a class="reference internal" href="../conf/"><span class="doc">Conferences</span></a>. (Talk about other conferences in <strong>#community-events</strong>.)</p></li> <li><p><strong>#meetups</strong> - Questions and discussion for Write the Docs <a class="reference internal" href="../meetups/"><span class="doc">Meetups</span></a>. (Talk about other meetups in <strong>#community-events</strong>.)</p></li> <li><p><strong>#watercooler</strong> - Off-topic chat. Get to know folks’ other interests that aren’t around documentation :)</p></li> </ul> </section> <section id="other-useful-topical-channels"> <h3>Other useful topical channels<a class="headerlink" href="#other-useful-topical-channels" title="Permalink to this heading">¶</a></h3> <ul class="simple"> <li><p><strong>#career-advice</strong> - Should you take that job? Am I being paid enough? Ask here!</p></li> <li><p><strong>#learn-tech-writing</strong> - Are you considering a job in documentation, or want to tune up your skills? Chat with experts and other learners here, and consider reading a tech writing-related book with the WTD book club!</p></li> <li><p><strong>#markup-the-docs</strong> - Talk about markup languages. Markdown, rST, Asciidoc, etc.</p></li> <li><p><strong>#documenting-apis</strong> - Talk about REST API’s. Swagger, Apiary, API Blueprint, and other API doc tools.</p></li> <li><p><strong>#sphinx</strong> - Talk about the Sphinx documentation generation tool.</p></li> <li><p><strong>#flare</strong> - Talk about the Flare documentation toolkit.</p></li> <li><p><strong>#confluence</strong> - Talk about everyone’s favorite Wiki.</p></li> <li><p><strong>#community-showcase</strong> - Announce your projects here! Blog posts, docs, code, products—whatever you make that you’re excited to share!</p></li> <li><p><strong>#community-help-wanted</strong> - Got an open-source project that needs docs contributors? Looking for open-source communities who will mentor you while you contribute to their docs? This channel is for you! Only for volunteer/unpaid work with open-source projects; companies and paid job postings should continue to use #job-posts-only.</p></li> <li><p><strong>#wtd-weps</strong> - Ask questions about the Write the Docs Enhancement Proposal (WEP) system and brainstorm on pre-proposal ideas to help improve our community processes and governance.</p></li> </ul> </section> <section id="channels-that-serve-specific-communities-their-allies"> <h3>Channels that serve specific communities & their allies<a class="headerlink" href="#channels-that-serve-specific-communities-their-allies" title="Permalink to this heading">¶</a></h3> <p>Allies are welcome as guests in these channels. Please be considerate.</p> <ul class="simple"> <li><p><strong>#bipoc</strong> - Social and discussion space for Write the Docs’ <a class="reference internal" href="../bipoc/"><span class="doc">BIPOC Documentarians</span></a> community.</p></li> <li><p><strong>#lgbtq</strong> - Social and discussion space for LGBTQ+ people in the WTD community.</p></li> </ul> </section> <section id="location-based-channels"> <h3>Location-based channels<a class="headerlink" href="#location-based-channels" title="Permalink to this heading">¶</a></h3> <p>We have too many location-based channels to list. Chances are we have a large group of folks in your area, so join up and chat with them. They’re a great way to get in touch with your local meetup organizer and community.</p> </section> <section id="creating-channels"> <h3>Creating channels<a class="headerlink" href="#creating-channels" title="Permalink to this heading">¶</a></h3> <p>If you didn’t see a channel that matches your interests, make sure to browse the complete channel list in Slack.</p> <p>If you still can’t find a suitable channel, you can propose a new channel. We use this process to help channels succeed at creating discussion and introducing documentarians to others who share their interests. To propose a channel:</p> <ol class="arabic simple"> <li><p>Find two other people to cosponsor your channel idea. Ask in related channels to find people who share your interest.</p></li> <li><p>Together, come up with a channel name and write a channel description.</p></li> <li><p>Post in <strong>#meta</strong> requesting a channel. Be sure to share your proposed channel name, description, and to tag your cosponsors.</p></li> <li><p>Start thinking about how to seed the new channel with discussion, with an open-ended question, a link to discuss, or a hot take.</p></li> </ol> <p>The Write the Docs moderation team will review your proposal to make sure the new channel will remain active and won’t duplicate or create confusion with another channel. Whenever possible, the moderators work with channel sponsors on improvements to the proposal.</p> <p>If your proposal is approved, then you and your consponsors must:</p> <ol class="arabic simple"> <li><p>Seed discussion in the new channel. A starter discussion helps others learn whether the channel is relevant to them and increases the number of documentarians who join the channel.</p></li> <li><p>Make an announcement in <strong>#general</strong> and channels related to the new channel’s topic. For example, if there’s a new a channel for underwater basket weaving, then make an announcement like “Join us in #underwater-basket-weaving to discuss techniques, materials, and what to store in all these baskets.”</p></li> </ol> </section> </section> <section id="guidelines"> <h2>Guidelines<a class="headerlink" href="#guidelines" title="Permalink to this heading">¶</a></h2> <p>Our goal with Write the Docs is to be <strong>the most welcoming community on the internet</strong>. People who are new to our community in particular should be assisted and welcomed.</p> <p>Our <a class="reference internal" href="../code-of-conduct/"><span class="doc">Code of Conduct</span></a> applies to all spaces associated with Write the Docs, which includes our Slack. In addition, we have several Slack-specific guidelines:</p> <section id="social-tips"> <h3>Social tips<a class="headerlink" href="#social-tips" title="Permalink to this heading">¶</a></h3> <p>To have good experiences on Slack, create the conversations you want to be a part of. You can help us do this by following these tips:</p> <ul class="simple"> <li><p><strong>Say hi.</strong> Don’t forget to introduce yourself in <code class="docutils literal notranslate"><span class="pre">#intros</span></code>. If you’ve been away a while, reintroduce yourself. The world is a better place with a flood of hello’s.</p></li> <li><p><strong>Use inclusive language.</strong> Our community is multicultural, multiracial, multigendered, and generally diverse. When posting in channels, avoid using words such as “guys” to address a mixed group; possible alternatives include “folks”, “everyone”, and “documentarians”.</p></li> <li><p><strong>Remember that we’re all documentarians.</strong> The Write the Docs community is much more than a space for technical writers. We welcome everyone who wants to learn more about creating documentation, including developers, testers, customer support agents, technical writers, program/product managers, developer relations specialists, and more.</p></li> <li><p><strong>Only participate when you can be constructive.</strong> Try to be constructive in all that you do, and otherwise consider not participating in a conversation.</p></li> <li><p><strong>Don’t be snarky.</strong> We are all trying the best we can.</p></li> <li><p><strong>Be careful with jokes.</strong> You know that you’re joking, but some people might take you seriously.</p></li> <li><p><strong>If you don’t have anything nice to say, don’t say anything at all.</strong></p></li> </ul> <p>We also recommend reading <a class="reference external" href="https://www.metafilter.com/microaggressions.mefi">Microaggressions: Making space for everybody</a>, which goes over how to avoid small slights and hurtful behaviors, especially against members of marginalized groups.</p> </section> <section id="online-community-issues"> <h3>Online community issues<a class="headerlink" href="#online-community-issues" title="Permalink to this heading">¶</a></h3> <p>There is a specific set of behaviors that is prevalent in online communities that we’d like to address, to make sure our community doesn’t fall into these traps. Please be mindful with the following behaviors:</p> <ul class="simple"> <li><p><strong>No shaming.</strong> There may be organizations, job functions, and tools that you don’t like. There is a good chance there is someone in the room who is closely connected to that thing you don’t like. Don’t make them feel bad; they are likely just in a different context.</p></li> <li><p><strong>Don’t criticize questions.</strong> Some people might ask incomplete questions that are hard to answer. If people ask questions that are simple to answer on Google, still answer them nicely. Ask follow up questions and act in good faith to help them solve their issues.</p></li> <li><p><strong>Avoid technology competitions.</strong> It doesn’t matter if your tool is faster or better in some metric. We care about creating great documentation for our users.</p></li> <li><p><strong>Honor the community’s trust and confidence.</strong> In the Write the Docs Slack, we are privileged to be able to discuss complex or sensitive situations with other docs practitioners. But those discussions can only happen in an environment of discretion and trust. The <a class="reference external" href="https://www.chathamhouse.org/about-us/chatham-house-rule">Chatham House Rule</a> applies: you’re welcome to use the information shared, but never reveal names, job titles, employers, or other identifying information about other participants outside of Slack, unless you’ve received their explicit permission to do so.</p></li> </ul> </section> <section id="posting-rules"> <h3>Posting rules<a class="headerlink" href="#posting-rules" title="Permalink to this heading">¶</a></h3> <p>The Write the Docs Slack hosts many documentarians and has few moderators. We expect everyone to follow these “rules of the road” at all times, to keep the conversation going smoothly and to reduce annoyances for everyone.</p> <ul class="simple"> <li><p><strong>Post as yourself, not as a brand.</strong> Write the Docs Slack accounts must be operated by an individual human being that exists outside of work. Leave the marketing language at work and talk to people like people, not a sales lead.</p></li> <li><p><strong>Start and stay on topic.</strong> Digressions happen, but don’t be afraid to move a conversation to a thread or another channel when it makes sense.</p></li> <li><p><strong>Focus on quality over quantity.</strong> Excessive crossposting or reposting can drown out other conversations and looks like spam. Send your message to the most-relevant channel then give some time for conversations to start before casting a wider net. Sometimes it makes sense to send a similar message to multiple channels at once, or to post again, but show restraint.</p></li> <li><p><strong>Include context with links.</strong> Give us your perspective: tell us what you’re sharing, why, and your connection to it. Don’t post a bare URL or use link shorteners: they’re not informative and look like spam.</p></li> <li><p><strong>Use content warnings and threads for sensitive topics.</strong> Write the Docs is a big community: topics that seem safe to you could make others feel uncomfortable or unwelcome. Help others choose which conversations they opt into by signposting sensitive or traumatic topics and confining them to threads.</p></li> </ul> <p>Posts not meeting these criteria may result in <a class="reference internal" href="#moderation-action"><span class="std std-ref">moderation action</span></a>, such as a warning or deletion.</p> </section> <section id="self-promotion-surveys-and-sales"> <h3>Self-promotion, surveys, and sales<a class="headerlink" href="#self-promotion-surveys-and-sales" title="Permalink to this heading">¶</a></h3> <p>You’re welcome to share, link to, and mention your own work, including blog posts, social media, events, and paid products or services. That said, posts where you stand to benefit from others’ money, personal information, attention, or labor come with higher expectations. When this applies, make sure you follow the general guidelines closely.</p> <p>In addition to the guidance that applies to all participants, we expect self-promotion on the Write the Docs Slack to follow these additional guidelines:</p> <ul class="simple"> <li><p><strong>Be transparent.</strong> Clearly explain what you are promoting, why it matters to documentarians, and your involvement (current/former employee, contractor, friend of a friend, etc.). Be up front about paywalls, registration requirements, referral benefits, or commissions. If you’re running a survey, say when and how the results will be published.</p></li> <li><p><strong>Give more than you take.</strong> Make self-promotion a reasonable proportion of your participation in the community. Too much self-promotion creates distrust and hostility. If you’re not sure if it’s too much, aim to help others 10 times for every time you self-promote.</p></li> <li><p><strong>Post publicly instead of sending direct messages (DMs)</strong>. A DM is like a home and you’re like a vampire: you’re not allowed in without an invitation. It can be tempting to DM people, but please respect their inboxes and post in public channels unless invited to DM.</p></li> <li><p><strong>Read the room.</strong> The Write the Docs Slack is informal and conversational; high-pressure sales aren’t welcome. If people aren’t interested in what you’re offering, don’t take it as a license to become louder and more aggressive. If you’re asked to stop, then stop.</p></li> <li><p><strong>Treat the community like friends, not customers.</strong> The community tends to ignore or spam report posts that look like sales pitches. Avoid calls to action — <a class="reference external" href="https://en.wikipedia.org/wiki/Call_to_action_(marketing)">attempts to prompt an immediate response or sale</a> — such as requests to “buy”, “subscribe”, “retweet”, or “share” (among others).</p></li> </ul> <section id="common-self-promotion-situations"> <h4>Common self-promotion situations<a class="headerlink" href="#common-self-promotion-situations" title="Permalink to this heading">¶</a></h4> <p>Here are some examples of common self-promotion situations and how to self-promote responsibly (and irresponsibly):</p> <ul> <li><p>You’ve written a blog post (Medium, Hashnode, etc.) that you want to share with the community, but it’s not closely related to an ongoing discussion.</p> <p><strong>Do</strong> share it in <strong>#community-showcase</strong> and tell us why it is relevant to the practice of writing, creating, maintaining, or building docs.</p> <p><strong>Don’t</strong> cross-post that content across multiple channels or use the <strong>#community-showcase</strong> (or any other) channel for link-farming or drive-by engagement only.</p> </li> <li><p>Your employer is hosting an event to promote their product or service (even if it’s not the primary purpose of the event).</p> <p><strong>Do</strong> share it in <strong>#community-events</strong> and tell others your connection to the event.</p> <p><strong>Don’t</strong> obscure the purpose of the event, your relationship to the employer, or the costs associated to attendance.</p> </li> <li><p>Someone else has asked a question and you’re the author of an article, blog, book, or similar resource that answers the question.</p> <p><strong>Do</strong> reply by briefly summarizing your work, noting your authorship, and linking to the resource.</p> <p><strong>Don’t</strong> cross-post a reply outside the thread or channel or send the person asking the question a direct message.</p> </li> <li><p>A moderator has raised one or more of your posts as violating the self-promotion guidelines, and provided you with feedback and guidance.</p> <p><strong>Do</strong> read the guidance, review our rules, and modify your posting patterns to respect the Write the Docs community.</p> <p><strong>Don’t</strong> use DMs, alt-accounts, clever interpretations of the rules/guidance, or other methods to ignore or get around the moderator feedback.</p> </li> </ul> </section> <section id="suggested-channels-for-self-promotion"> <h4>Suggested channels for self-promotion<a class="headerlink" href="#suggested-channels-for-self-promotion" title="Permalink to this heading">¶</a></h4> <p>Here are some channels specifically for wholesome self-promotion:</p> <ul class="simple"> <li><p><strong>#job-posts-only</strong> is the best place to post paid jobs.</p></li> <li><p><strong>#freelance</strong> is the best place to post freelance projects.</p></li> <li><p><strong>#community-events</strong> (formerly known as <cite>#calls-for-papers</cite>) is a good place to announce non-Write the Docs events.</p></li> <li><p><strong>#community-help-wanted</strong> is a good place to share surveys, calls for research interview subjects, and calls for participation on open-source projects.</p></li> <li><p><strong>#community-showcase</strong> is a space for responsible self-promotion.</p></li> </ul> <p>Posts in those channels not meeting the posting rules may result in <a class="reference internal" href="#moderation-action"><span class="std std-ref">moderation action</span></a>, such as a warning or deletion.</p> </section> </section> <section id="reporting-issues"> <h3>Reporting Issues<a class="headerlink" href="#reporting-issues" title="Permalink to this heading">¶</a></h3> <p>If you see a message in a public channel that needs moderator attention, you can react to it with the <code class="docutils literal notranslate"><span class="pre">:attn-mods:</span></code> or <code class="docutils literal notranslate"><span class="pre">:spam:</span></code> reactji. Note that this is a public action, so only take it if you’re okay with the poster seeing you have done this.</p> <p>If you see people not following the behavior guidelines you can:</p> <ul class="simple"> <li><p>Ask the participant to change their behavior by referring to this guide and explaining why what they said might have been hurtful.</p></li> <li><p>Ask the <a class="reference internal" href="../team/#moderation-team"><span class="std std-ref">moderation team</span></a> (in the <strong>#meta</strong> channel or by DM) to address the situation. Include a link or screenshot of the conversation, if possible.</p></li> </ul> </section> <section id="moderation-action"> <span id="id2"></span><h3>Moderation action<a class="headerlink" href="#moderation-action" title="Permalink to this heading">¶</a></h3> <p>The role of the moderation team is to keep healthy conversation going and set expectations by example. When that fails, we have a few tools to help set things right: private and public cautions, message deletion, and temporary or permanent bans.</p> <p>Unfortunately, the guidelines above don’t cover every scenario. If something is going on that gives the community or moderators headaches, we’ll take action, even if there’s no specific rule violation to point to.</p> <p>When we take action, it’s usually in the form of a private message to ask someone to change their behavior. We try to discourage or encourage specific behaviors, not make judgments on people, for the benefit of the whole community.</p> <p>If you get a message from us, it might be about your behavior, but it’s not about <em>you</em> as a person. If something goes wrong, we’ll tell you about it and try to help you avoid the problem in the future. Help us help the community.</p> </section> <section id="credit"> <h3>Credit<a class="headerlink" href="#credit" title="Permalink to this heading">¶</a></h3> <p>This concept is inspired by the <a class="reference external" href="https://www.recurse.com/manual#sub-sec-social-rules">Recurse Center’s Social Rules</a>. Thanks for the inspiration!</p> </section> </section> </section> <div class="section"> </div> </div> </div> </div> <div class="sphinxsidebar" role="navigation" aria-label="main navigation"> <div class="sphinxsidebarwrapper"> <p class="logo"> <a href="../"> <img class="logo" src="../_static/sticker-wtd-colors.png" alt="Logo" /> </a> </p> <br> <p> Write the Docs is a global community of people who care about documentation. We have a Slack community, conferences on 3 continents, and local meetups! </p> <div id="searchbox" style="display: none" role="search"> <h3 id="searchlabel">Quick search</h3> <div class="searchformwrapper"> <form class="search" action="../search/" method="get"> <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/> <input type="submit" value="Go" /> </form> </div> </div> <script>document.getElementById('searchbox').style.display = "block"</script><style> .ethical-alabaster::before {margin-top: 1em;} </style> <div id="ethical-ad-placement"></div> <div id="toc"> <h3>Site Content</h3> <ul class="current"> <li class="toctree-l1"><a class="reference internal" href="../surveys/">Salary Surveys</a></li> <li class="toctree-l1"><a class="reference internal" href="../guide/">Software documentation guide</a></li> <li class="toctree-l1"><a class="reference internal" href="../book-club/">Book Club</a></li> <li class="toctree-l1"><a class="reference internal" href="../hiring-guide/">Hiring guide</a></li> <li class="toctree-l1 current"><a class="reference internal" href="../about/stay-connected/">Stay Connected</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/about-the-org/">About Our Organization</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/events-activities/">Events and Activities</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/learning-resources/">Learning Resources</a></li> </ul> </div> <br> <h3>Join our mailing list</h3>  <link href="//cdn-images.mailchimp.com/embedcode/classic-071822.css" rel="stylesheet" type="text/css"> <style type="text/css"> #mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif;} /* Add your own Mailchimp form style overrides in your site stylesheet or in this style block. We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */ </style> <div id="mc_embed_signup"> <form action="https://writethedocs.us6.list-manage.com/subscribe/post?u=94377ea46d8b176a11a325d03&id=dcf0ed349b&f_id=00d2c2e1f0" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate> <div id="mc_embed_signup_scroll"> <div class="mc-field-group"> <label for="mce-EMAIL">Email Address <span class="asterisk">*</span> </label> <input type="email" value="" name="EMAIL" class="required email" id="mce-EMAIL" required> <span id="mce-EMAIL-HELPERTEXT" class="helper_text"></span> </div> <div class="mc-field-group input-group"> <strong>What types of updates would you like? </strong> <ul><li> <input type="checkbox" value="1" name="group[14633][1]" id="mce-group[14633]-14633-0" checked> <label for="mce-group[14633]-14633-0">Monthly Community Newsletter</label> </li> <li> <input type="checkbox" value="2" name="group[14633][2]" id="mce-group[14633]-14633-1"> <label for="mce-group[14633]-14633-1">North American Conference Announcements</label> </li> <li> <input type="checkbox" value="4" name="group[14633][4]" id="mce-group[14633]-14633-2"> <label for="mce-group[14633]-14633-2">European Conference Announcements</label> </li> <li> <input type="checkbox" value="8" name="group[14633][8]" id="mce-group[14633]-14633-3"> <label for="mce-group[14633]-14633-3">Australian Conference Announcements</label> </li> <li> <input type="checkbox" value="16" name="group[14633][16]" id="mce-group[14633]-14633-4"> <label for="mce-group[14633]-14633-4">Atlantic Conference Announcements</label> </li> </ul> <span id="mce-group[14633]-HELPERTEXT" class="helper_text"></span> </div> <div id="mce-responses" class="clear"> <div class="response" id="mce-error-response" style="display:none"></div> <div class="response" id="mce-success-response" style="display:none"></div> </div>  <div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_94377ea46d8b176a11a325d03_dcf0ed349b" tabindex="-1" value=""></div> <div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div> </div> </form> </div>  </div> </div> <div class="clearer"></div> </div> <style> /* Sponsors */ .sponsors { float: left; margin-top: 12px; text-align: center; } .sponsors .sponsor { display: inline-block; text-align: center; text-decoration: none; padding: 10px; } .sponsors .sponsor img { width: 90px; height: auto; } .sponsors .sponsor-name { font-size: 12px; } .sponsors .sponsor-description { font-size: 10px; color: #BCC1C3; } .sponsors .sponsor-name, .sponsors .sponsor-description { text-align: center; line-height: 1.4; } /* Links in footer */ .footer-links { display: flex; justify-content: space-between; gap: 1rem; } #social-footer { line-height: 1.5rem; } div.footer,div.footer a { color: #757575; } </style> <div class="footer"> <div class="container footer-links"> <div style="flex-basis: 20rem; text-align: left;"> <span>© Write the Docs</span> <span>  <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0; vertical-align: middle;" src="https://i.creativecommons.org/l/by-nc-sa/4.0/80x15.png" /></a> </span> </div> <div id="social-footer"> <span><a href="/contact/"><i class="iconf-email"></i>Contact Us</a></span> | <span><a href="/site-map"><i class="iconf-github-circled-alt2"></i>Site map</a></span> | <span><a href="https://github.com/writethedocs"><i class="iconf-github-circled-alt2"></i>GitHub</a></span> | <span><a href="https://twitter.com/writethedocs"><i class="iconf-twitter-circled"></i>Twitter</a></span> | <span> <a href="https://www.linkedin.com/company/write-the-docs"> LinkedIn </a> </span> | <span><a href="../code-of-conduct/">Code of Conduct</a></span> | </div> </div> <div class="sponsors" id="community-sponsors" style="width: 100%;"> <hr> <a class="sponsor" href="https://readthedocs.org" rel="noopener" target="_blank"> <img src="https://read-the-docs-guidelines.readthedocs-hosted.com/_images/logo-wordmark-dark.png" alt="Read the Docs" class="sponsor-image"> <div class="sponsor-name">Read the Docs</div> <div class="sponsor-description">Website Hosting</div> </a> <a class="sponsor" href="https://www.gitbook.com/?utm_campaign=launch&utm_medium=display&utm_source=write_the_docs&utm_content=ad" rel="noopener" target="_blank"> <img src="/_static/img/sponsors/gitbook.png" alt="GitBook" class="sponsor-image"> <div class="sponsor-name">GitBook</div> <div class="sponsor-description">Community sponsor</div> </a> <a class="sponsor" href="../sponsorship/" rel="noopener" target="_blank"> <div class="sponsor-name">Sponsorship Info</div> </a> </div> </div>  <script async defer src="https://scripts.simpleanalyticscdn.com/latest.js"></script> <noscript><img src="https://queue.simpleanalyticscdn.com/noscript.gif" alt="" referrerpolicy="no-referrer-when-downgrade" /></noscript> </body> </html>