<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text">Blog - Posts by Write the Docs Team</title>
  <id>https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml</id>
  <updated>2021-12-06T00:00:00Z</updated>
  <link href="https://www.writethedocs.org/" />
  <link href="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml" rel="self" />
  <generator uri="https://ablog.readthedocs.org" version="0.10.6">ABlog</generator>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Write the Docs Newsletter – December 2021</title>
    <id>https://www.writethedocs.org/blog/newsletter-december-2021/</id>
    <updated>2021-12-06T00:00:00Z</updated>
    <published>2021-12-06T00:00:00Z</published>
    <link href="https://www.writethedocs.org/blog/newsletter-december-2021/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;write-the-docs-newsletter-december-2021&quot;&gt;

&lt;p&gt;Hey everyone,&lt;/p&gt;
&lt;p&gt;The year is drawing to a close - thank goodness, if you ask me - and we’re back with the very last edtion of the newsletter for 2021. It’s been a _complicated_ year but not without its highlights - our second year of virtual conferences plus the just-wrapped-up Australia super-meetup. Thanks for being such a great community through it all 💖&lt;/p&gt;
&lt;p&gt;One last call for folks who haven’t yet filled out the &lt;a class=&quot;reference external&quot; href=&quot;https://salary-survey.writethedocs.org/&quot;&gt;Salary Survey&lt;/a&gt;. We’d love it if you would consider contributing the details of your compensation. It’s all anonymous and the anonymised results are released for free, so everyone in the community can benefit. &lt;a class=&quot;reference external&quot; href=&quot;https://salary-survey.writethedocs.org/&quot;&gt;Fill it out here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;With that, on to our articles from this month!&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;the-work-documentation-really-requires-it-s-not-all-writing&quot;&gt;
&lt;h2&gt;The work documentation really requires (it’s not all writing!)&lt;/h2&gt;
&lt;p&gt;A plaintive question about how to develop content more efficiently produced a perhaps surprising set of responses. The original poster framed their challenge in terms of research that delays the writing process, but replies tended to point out that research is a key part of creating any documentation. If your research is inefficient – if you’re falling down “useless rabbit holes” as one poster put it – you could consider pruning your sources, or working more from summaries than from long-form reads.&lt;/p&gt;
&lt;p&gt;Generally, though, folks agreed that research and other supporting activities form the bulk of the work they do to produce docs – actual writing takes up relatively little time overall. In addition to research, testing/QA, wrangling reviews and tooling, managing content beyond the writing (structure, metadata, etc) all showed up on lists of docs work beyond writing. So maybe when we’re not writing we’re still as efficient as we can be?&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;deciding-what-to-work-on-next&quot;&gt;
&lt;h2&gt;Deciding what to work on next&lt;/h2&gt;
&lt;p&gt;What should you do when you aren’t sure what to do next? Many of us have an abundance of pending docs work, but the most important task in your pile depends on the particulars of your situation. If you’re having trouble prioritizing docs tasks, try reading product and engineering plans. These are valuable resources for learning what’s important at your company, and the insights you pick up can inform your priorities in the documentation realm.&lt;/p&gt;
&lt;p&gt;Of course, more general suggestions usually have wider applicability, so here’s a handful of other good ideas from the Write the Docs community:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Review help tickets from customers and audit your information architecture to learn about potential gaps in your docs coverage.&lt;/li&gt;
&lt;li&gt;Test your toolchain and processes for storing and maintaining docs to find problems you can resolve. You might also find some automation opportunities.&lt;/li&gt;
&lt;li&gt;Inspect internal documentation for maintenance issues – internal docs are often created and forgotten.&lt;/li&gt;
&lt;li&gt;Create a company style guide, if you don’t already have one, and apply it throughout the docs.&lt;/li&gt;
&lt;li&gt;Map or document your team workflows, docs resources and processes, and organization charts.&lt;/li&gt;
&lt;li&gt;As time allows, learn a new tool or technology to enrich your skills. For example, you could investigate different ways to communicate concepts, like animation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;One more tip: our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/blog/newsletter-june-2021/&quot;&gt;June 2021 newsletter&lt;/a&gt; included a relevant item about balancing writing new docs with ongoing docs maintenance, which may also be helpful.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;answers-to-why-are-good-docs-important&quot;&gt;
&lt;h2&gt;Answers to “Why are good docs important?”&lt;/h2&gt;
&lt;p&gt;What is the importance of good documentation? This question can come up a lot - during an interview, project planning, or just a chat with a colleague. Do you have a good answer?&lt;/p&gt;
&lt;p&gt;You’ve got plenty of options. For example, that good documentation eases the strain on the support staff or minimizes friction for customers, enabling them to complete tasks quickly. Or even more ideas: that good documentation acts as a sales tool, helping with both advertising and lead generation; it shows product commitment, and helps close profitable deals with potential customers. It’s also valuable internally as a source of truth, allowing everyone in the organization to work smarter rather than harder.&lt;/p&gt;
&lt;p&gt;For more on this, Lari Maza discusses good documentation in her article &lt;a class=&quot;reference external&quot; href=&quot;https://medium.com/larimaza-en/how-to-write-good-documentation-e19c70dc67f0&quot;&gt;“How to Write Good Documentation”&lt;/a&gt;. According to Maza, writers should anticipate customer questions, keep within scope, and expand information with links and images.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;standards-in-documentation-tooling&quot;&gt;
&lt;h2&gt;Standards in documentation tooling&lt;/h2&gt;
&lt;p&gt;We had a great discussion this month about the fragmentation of docs-as-code tooling, sparked by &lt;a class=&quot;reference external&quot; href=&quot;https://passo.uno/docs-as-code-tools-open-standards/&quot;&gt;Fabrizio Ferri-Benedetti’s article&lt;/a&gt;. The article talks about the often-fragile docs-as-code toolchains that companies run for themselves. When tools are hard to maintain or don’t work well, they hinder growth, speed, and collaboration. He argues that these problems are caused by systemic issues: we’re missing a standard markup language, universal documentation rendering, and a version control system designed for docs.&lt;/p&gt;
&lt;p&gt;Documentation rendering was contentious, but folks saw more promise in the markup idea. DITA is heavyweight; Markdown lets you get on with writing, but is neither standardised nor designed for docs; and the alternatives aren’t widely used. Some community members defended AsciiDoc as meeting all the criteria - it’s interesting that it’s currently going through &lt;a class=&quot;reference external&quot; href=&quot;https://projects.eclipse.org/projects/asciidoc.asciidoc-lang&quot;&gt;a standardization process via Eclipse&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The article’s main problem with Git, often expressed by writers as well as developers, is that it is hard to learn. There is a counter-argument to needing a new system: instead, we should take the tools we have, but make them work better for use cases. Perhaps we don’t need a new version control system, but better Git clients designed for docs workflows…&lt;/p&gt;
&lt;p&gt;But some folks disagreed with the premise that standardisation will help. Not least because creating new standards &lt;a class=&quot;reference external&quot; href=&quot;https://xkcd.com/927/&quot;&gt;can make things worse&lt;/a&gt;! And how can we standardise if we don’t have any universal best practices? Perhaps, for docs problems, there is no “one best way” - you’ll always have to adapt your tools to different use cases; sometimes what you really need is the feature set of a Help Authoring Tool like Flare. Or perhaps we should all just give up and use Word? (joking, joking!)&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;what-were-reading-and-watching&quot;&gt;
&lt;h2&gt;What we’re reading and watching&lt;/h2&gt;
&lt;p&gt;The #bipoc group’s been discussing the following materials on diversity, inclusion, and equity. Want to join the conversation? Please join us in the &lt;a class=&quot;reference external&quot; href=&quot;https://app.slack.com/client/T0299N2DL/C016STMEWJD&quot;&gt;#bipoc Slack channel&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;A short read: Over at Tech Crunch, &lt;a class=&quot;reference external&quot; href=&quot;https://techcrunch.com/2021/11/16/why-dei-programs-are-failing/&quot;&gt;Why DEI programs are failing&lt;/a&gt; discusses the shortcomings of DEI programs and how ERGs might be the answer.&lt;/p&gt;
&lt;p&gt;A longer read: A little old, but still relevant, last year’s &lt;a class=&quot;reference external&quot; href=&quot;https://www.mckinsey.com/featured-insights/diversity-and-inclusion/diversity-wins-how-inclusion-matters&quot;&gt;McKinsey and Company’s 2020 report on Diversity and Inclusion&lt;/a&gt; concludes that companies investing in DE&amp;amp;I are more profitable than those that are not. You can download the full report at the end of the summary.&lt;/p&gt;
&lt;p&gt;For a longer time investment: Check out &lt;a class=&quot;reference external&quot; href=&quot;https://www.diversityincbestpractices.com/webinar-recap-lets-talk-microaggressions/&quot;&gt;Diversity Inc Best Practices’ Webinar Recap: Let’s talk Microagressions&lt;/a&gt;. In this webinar, the panelists define microaggressions, discuss when they first encountered them, how to respond to them, and what their companies are doing to combat them.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;from-our-sponsors&quot;&gt;
&lt;h2&gt;From our sponsors&lt;/h2&gt;
&lt;p&gt;This month’s newsletter is sponsored by &lt;a class=&quot;reference external&quot; href=&quot;https://www.gatewaytranslations.net/en/&quot;&gt;Gateway Translations&lt;/a&gt;:&lt;/p&gt;
&lt;hr&gt;
&lt;table width=&quot;100%&quot; border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;width:100%; max-width: 600px;&quot;&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td width=&quot;75%&quot;&gt;
          &lt;p&gt;
          Gateway Translations makes it easy for tech writers to get started with localization.
          &lt;/p&gt;
          &lt;ul&gt;&lt;li&gt;
          Finding the right translation tool with integrations for easy workflow &amp; file compatibility
          &lt;/li&gt;&lt;li&gt;
          Translators with technical backgrounds for 45 languages
          &lt;/li&gt;&lt;li&gt;
          Trusted by GitHub, TIBCO, Fortune 500s
          &lt;/li&gt;&lt;/ul&gt;
          &lt;/p&gt;&lt;p&gt;
          Book a &lt;a href=&quot;https://www.gatewaytranslations.net/en/localization-consultation-write-the-docs/&quot;&gt;free consultation&lt;/a&gt;.
          &lt;/p&gt;
      &lt;/td&gt;
      &lt;td width=&quot;25%&quot;&gt;
        &lt;a href=&quot;https://www.gatewaytranslations.net/en/&quot;&gt;
          &lt;img style=&quot;margin-left: 15px;&quot; alt=&quot;Gateway Translations&quot; src=&quot;/_static/img/sponsors/gateway.png&quot;&gt;
        &lt;/a&gt;
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;&lt;p&gt;&lt;em&gt;Interested in sponsoring the newsletter? Take a look at our&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;/sponsorship/newsletter/&quot;&gt;sponsorship prospectus&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;featured-job-posts&quot;&gt;
&lt;h2&gt;Featured job posts&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/549/staff-technical-writer/&quot;&gt;Staff Technical Writer&lt;/a&gt;, Netlify (remote - North America)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/539/senior-technical-writer/&quot;&gt;Senior Technical Writer&lt;/a&gt;,  Grid.ai Inc (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/542/technical-content-marketer/&quot;&gt;Technical Content Marketer&lt;/a&gt;, Okteto (remote)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;To apply for these jobs and more, visit the&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/&quot;&gt;Write the Docs job board&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;virtual-events-coming-up&quot;&gt;
&lt;h2&gt;Virtual events coming up&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;07 December, 08:30 EST (Florida, US) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/write-the-docs-florida/events/280769273&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;09 December, 19:00 CET (Barcelona, Spain) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Barcelona/events/282186027&quot;&gt;Working remotely from your team&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;14 December, 08:00 PST (Seattle, US) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-The-Docs-Seattle/events/282133165&quot;&gt;WtD Seattle: Casual Caffeine Hour&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Write the Docs Newsletter – November 2021</title>
    <id>https://www.writethedocs.org/blog/newsletter-november-2021/</id>
    <updated>2021-11-03T00:00:00Z</updated>
    <published>2021-11-03T00:00:00Z</published>
    <link href="https://www.writethedocs.org/blog/newsletter-november-2021/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;write-the-docs-newsletter-november-2021&quot;&gt;

&lt;p&gt;Hi folks! November has somehow rolled around (already??) and it’s that newsletter time of the month again.&lt;/p&gt;
&lt;p&gt;As promised last time: I’m super excited to let you know that the &lt;a class=&quot;reference external&quot; href=&quot;https://salary-survey.writethedocs.org/&quot;&gt;Salary Survey is now live&lt;/a&gt;. It takes less than ten minutes to complete, so please consider filling it out - you’ll be contributing to a really valuable resource for documentarians. All responses are completely anonymous, and we’re very careful not to publish any personally identifiable information (given the small size of the community). If you’re up for it, &lt;a class=&quot;reference external&quot; href=&quot;https://salary-survey.writethedocs.org/&quot;&gt;fill it out here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Plus, great news from down under - we’ve just announced the Australia and India meetup will be on December 3rd. This “super-meetup” will be a two-hour event with four fab speakers, and will be free to attend. &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Australia/events/280829245/&quot;&gt;Sign up for the event here&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;And with that, let’s take a look at what everyone’s been discussing on Slack…&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;managing-when-your-manager-lacks-docs-experience&quot;&gt;
&lt;h2&gt;Managing when your manager lacks docs experience&lt;/h2&gt;
&lt;p&gt;This month, our documentarians discussed how they have handled differences with a manager who has no experience with documentation. Among those who have worked for managers without a docs background, there were roughly two groups: the manager either deferred to the technical writer’s expertise or did not.&lt;/p&gt;
&lt;p&gt;If your manager is in the first category, you’ll likely encounter less heavy-handed supervision, and docs-related disagreements may be rare. If your manager is in the second category, you have a harder path to tread, especially when your manager’s perspective on docs-related tasks doesn’t quite match yours.&lt;/p&gt;
&lt;p&gt;In the course of this conversation, we learned a new acronym: HiPPO, meaning “highest paid person’s opinion.” In this context, the HiPPO method means ultimately disagreements between tech writers and managers are resolved according to the more senior person’s opinion, regardless of whether they have docs experience. When you are subject to the HiPPO method, your ability to affect docs-related decisions depends on how firmly you can gain your manager’s trust.&lt;/p&gt;
&lt;p&gt;Even when your manager is inclined to trust your ability, you’ll still need to confirm their confidence by doing good work, cooperating with the rest of the team, and meeting deadlines. This approach is the best path you can take with managers who don’t grasp your ability either – demonstrating that you understand and can document complex processes might be the only way you can get traction.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;options-for-single-sourcing&quot;&gt;
&lt;h2&gt;Options for single-sourcing&lt;/h2&gt;
&lt;p&gt;Single-source publishing is a content management technique that lets you use one source of content but publish it to different output formats (“write once, publish everywhere”). It’s not something that every team needs, but it can be super useful if you need to publish to the web &lt;em&gt;and&lt;/em&gt; PDFs, or if you have many similar variants on one product. If your team is not “technical” - more specifically if they are unfamiliar with version control software like Git, lack software development skills, or have no way of obtaining the support necessary to implement a docs-as-code approach, component content management systems (CCMS) like Paligo and MadCap Flare might be more suitable.&lt;/p&gt;
&lt;p&gt;Regardless of the method you choose, decide on a single-source publishing strategy and consider the advantages and disadvantages of each option to determine which is ideal for your team. Distributed contributions, for example, may be a reason to choose the docs-as-code method. In contrast, if you use Flare or a docs-focused CMS like Knowledge Owl, you’ll find more robust support for reusing articles or snippets. Whatever method or tool you choose, have a plan in place to ensure a successful single-source publishing approach.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;documentation-gets-respect-or-at-least-attention&quot;&gt;
&lt;h2&gt;Documentation gets respect (or at least attention)&lt;/h2&gt;
&lt;p&gt;Two recent reports highlight the increased attention documentation seems to be getting in the worlds of software development.&lt;/p&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://cloud.google.com/devops/state-of-devops&quot;&gt;2021 State of DevOps report from Google Cloud&lt;/a&gt; includes data showing the effects of docs quality on devops team performance, and describes practices to improve the quality of your documentation. The report is based on seven years of research and data from more than 32,000 professionals worldwide, focusing on “capabilities and practices that drive software delivery, operation, and organizational performance.” So the focus is not on docs – but the report includes good documentation as one of six findings characteristic of the 26% of teams studied who fall into the highest performing category. This is _internal_ documentation, and its quality has a statistically significant impact on how secure, reliable, and effective a team’s devops practices are. Quality documentation efforts should include critical use cases for products and services, guidelines for updating and editing existing documentation, clearly defined ownership and responsibility for documentation, inclusion of docs as part of the software development process, and recognition of docs work during performance reviews and promotions.&lt;/p&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://smartbear.com/state-of-software-quality/api/&quot;&gt;State of Software Quality API 2021 report&lt;/a&gt; from SmartBear similarly points to “accurate and detailed documentation” as a key aspect of the overall success of an API, second only to “ease of use” for API consumers. Disappointingly few survey respondents rated their API docs as “Very Good” – but only 16% of teams include technical writers for their API docs. On the other hand, more than half the respondents contribute to API docs in some way, and 60-70% of respondents work for companies that include a formal API documentation process – but only about half of those companies consider documentation a priority. Respondents cited a range of obstacles to providing quality documentation, but they all fell into the larger category of insufficient resources – time, tools, personnel, budget, and more. On another front, our documentarians who so diligently work with OpenAPI definitions will be happy to read that OpenAPI usage continues high, but GraphQL and AsyncAPI continue to grow in popularity.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;what-were-reading-and-listening-to&quot;&gt;
&lt;h2&gt;What we’re reading and listening to&lt;/h2&gt;
&lt;p&gt;The #bipoc group’s been discussing the following materials on diversity, inclusion, and equity. Want to join the conversation? Please join us in the &lt;a class=&quot;reference external&quot; href=&quot;https://app.slack.com/client/T0299N2DL/C016STMEWJD&quot;&gt;#bipoc Slack channel&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;This month’s articles are &lt;a class=&quot;reference external&quot; href=&quot;https://www.merriam-webster.com/dictionary/intersectionality&quot;&gt;intersectional&lt;/a&gt;. They touch on topics that intersect gender identity and people of color.&lt;/p&gt;
&lt;p&gt;A short read: A topic of discussion that’s come up in the Write the Docs Slack, is it ok to address a group of people as “you guys”? Baron Schwartz &lt;a class=&quot;reference external&quot; href=&quot;https://www.xaprb.com/blog/you-guys/&quot;&gt;sums up arguments from the internet&lt;/a&gt; and offers some alternatives.&lt;/p&gt;
&lt;p&gt;A medium read: In the article &lt;a class=&quot;reference external&quot; href=&quot;https://hbr.org/2021/02/stop-telling-women-they-have-imposter-syndrome&quot;&gt;Stop Telling Women They Have Imposter Syndrome&lt;/a&gt; from the Harvard Business Review, Ruchika Tulshyan and Jodi-Ann Burey talk about the myth of Imposter Syndrome and how it’s disproportionately hurting women of color in the workplace.&lt;/p&gt;
&lt;p&gt;A longer read/listen: This year the &lt;a class=&quot;reference external&quot; href=&quot;https://www.mckinsey.com/featured-insights/diversity-and-inclusion/women-in-the-workplace&quot;&gt;McKinsey and Company’s Women in the Workplace report&lt;/a&gt; highlights that women, while making some gains in the workplace, are still facing challenges when trying to rise to higher levels. This is especially true for women of color. Despite the increase of self-reported white allyship and an increase in DEI initiatives, women of color report continued micro-aggressions in the workplace and little allyship action from their peers.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;from-our-sponsors&quot;&gt;
&lt;h2&gt;From our sponsors&lt;/h2&gt;
&lt;p&gt;This month’s newsletter is sponsored by &lt;a class=&quot;reference external&quot; href=&quot;https://www.gatewaytranslations.net/en/&quot;&gt;Gateway Translations&lt;/a&gt; and JetBrains:&lt;/p&gt;
&lt;hr&gt;
&lt;table width=&quot;100%&quot; border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;width:100%; max-width: 600px;&quot;&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td width=&quot;75%&quot;&gt;
          &lt;p&gt;
          Gateway Translations makes it easy for tech writers to get started with localization.
          &lt;/p&gt;
          &lt;ul&gt;&lt;li&gt;
          Finding the right translation tool with integrations for easy workflow &amp; file compatibility
          &lt;/li&gt;&lt;li&gt;
          Translators with technical backgrounds for 45 languages
          &lt;/li&gt;&lt;li&gt;
          Trusted by GitHub, TIBCO, Fortune 500s
          &lt;/li&gt;&lt;/ul&gt;
          &lt;/p&gt;&lt;p&gt;
          Book a &lt;a href=&quot;https://www.gatewaytranslations.net/en/localization-consultation-write-the-docs/&quot;&gt;free consultation&lt;/a&gt;.
          &lt;/p&gt;
      &lt;/td&gt;
      &lt;td width=&quot;25%&quot;&gt;
        &lt;a href=&quot;https://www.gatewaytranslations.net/en/&quot;&gt;
          &lt;img style=&quot;margin-left: 15px;&quot; alt=&quot;Gateway Translations&quot; src=&quot;/_static/img/sponsors/gateway.png&quot;&gt;
        &lt;/a&gt;
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;
&lt;table width=&quot;100%&quot; border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;width:100%; max-width: 600px;&quot;&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td width=&quot;75%&quot;&gt;
          &lt;p&gt;
          'And what is the use of a book,' thought Alice 'without pictures or conversation?' Tech documentation is also more appealing and easy-to-read when illustrated. What visuals do we insert in our docs? What tools do we use to create and edit them? Help us by taking this survey, and we’ll be happy to share the results with you.
          &lt;/p&gt;&lt;p&gt;
          &lt;a href=&quot;https://jb.gg/WTD&quot;&gt;Take the survey&lt;/a&gt;
          &lt;/p&gt;
      &lt;/td&gt;
      &lt;td width=&quot;25%&quot;&gt;
        &lt;a href=&quot;https://jb.gg/WTD&quot;&gt;
          &lt;img style=&quot;margin-left: 15px;&quot; alt=&quot;SPONSOR&quot; src=&quot;/_static/img/sponsors/jetbrains-survey.png&quot;&gt;
        &lt;/a&gt;
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;&lt;p&gt;&lt;em&gt;Interested in sponsoring the newsletter? Take a look at our&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;/sponsorship/newsletter/&quot;&gt;sponsorship prospectus&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;featured-job-posts&quot;&gt;
&lt;h2&gt;Featured job posts&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/528/technical-content-writer/&quot;&gt;Technical Content Writer&lt;/a&gt;, Webiny (Remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/527/senior-technical-writer-web-developer/&quot;&gt;Senior Technical Writer (Web Developer)&lt;/a&gt;, Sitecore (National Capital Region, Canada)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/526/senior-technical-writer/&quot;&gt;Senior Technical Writer&lt;/a&gt;, Synctera (Remote - US or Canada)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/519/senior-technical-writer-at-privacera/&quot;&gt;Senior Technical Writer&lt;/a&gt;, Privacera (Remote - US)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;To apply for these jobs and more, visit the&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/&quot;&gt;Write the Docs job board&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;virtual-events-coming-up&quot;&gt;
&lt;h2&gt;Virtual events coming up&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;09 November, 08:30 EST (Florida, USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/write-the-docs-florida/events/280769082&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;09 November, 19:00 MST (Calgary, Canada) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/wtd-calgary/events/281618588&quot;&gt;A crash course in content reuse&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;16 November, 18:00 PST / 21:00 EST (USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/virtual-write-the-docs-west-coast-quorum/events/281680933&quot;&gt;A conversation with the authors of Docs for Developers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;17 November, 19:00 EST (Toronto, Canada) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Toronto/events/281410168&quot;&gt;Write the Docs Toronto&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;23 November, 08:30 EST (Florida, USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/write-the-docs-florida/events/280769269&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;03 December, 15:00 AEDT (Australia) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Australia/events/280829245&quot;&gt;Virtual super-meetup: WTD Australia and India 2021&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Conference highlights and thanks to the community!</title>
    <id>https://www.writethedocs.org/conf/prague/2021/news/thank-you-recap/</id>
    <updated>2021-10-13T00:00:00Z</updated>
    <published>2021-10-13T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/prague/2021/news/thank-you-recap/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;conference-highlights-and-thanks-to-the-community&quot;&gt;

&lt;p&gt;Hey everyone,&lt;/p&gt;
&lt;p&gt;The Write the Docs team is now emerging from the post-conference recovery period, and we wanted to send out a quick message to thank everyone for helping to make our conference such a success.
We appreciate everyone who makes the conference possible: speakers, sponsors, organizers, and attendees alike.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;conference-recap&quot;&gt;
&lt;h2&gt;Conference recap&lt;/h2&gt;
&lt;p&gt;At &lt;strong&gt;nearly 300 attendees&lt;/strong&gt;, the conference was active and full of usual mix of talks on the main stage along with Q&amp;amp;A, lightning talks, unconference sessions, writing sprints, social event, and job fair.
We thought everything went pretty smoothly this year, including experiments like the new social event platform.&lt;/p&gt;
&lt;p&gt;As always, we were excited with how our awesome community come together in our virtual venue. Lots of knowledge was shared, and we had a great time.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;talk-videos&quot;&gt;
&lt;h2&gt;Talk videos&lt;/h2&gt;
&lt;p&gt;Videos of the talks are now available on &lt;a class=&quot;reference external&quot; href=&quot;https://www.youtube.com/playlist?list=PLZAeFn6dfHpnaoiOQyd9BYbQbprDGQjQ9&quot;&gt;YouTube&lt;/a&gt;. This includes all conference talks and Q&amp;amp;A, as well as the lightning talks.
You can also subscribe to our &lt;a class=&quot;reference external&quot; href=&quot;https://www.youtube.com/writethedocs&quot;&gt;YouTube channel&lt;/a&gt; so you don’t miss any future content.
We are also working to add the videos and sketchnotes for all the talks to our website archive, so stay tuned for updates.&lt;/p&gt;
&lt;p&gt;Thanks again to all our presenters and moderators! Huge thanks also to &lt;a class=&quot;reference external&quot; href=&quot;https://www.bartatwork.com/&quot;&gt;Bart at Work&lt;/a&gt; for handling the A/V production on our event, it was flawless once again this year.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;shirts-still-on-sale&quot;&gt;
&lt;h2&gt;Shirts still on sale&lt;/h2&gt;
&lt;p&gt;If you want a souvenir from this year’s conference, our &lt;a class=&quot;reference external&quot; href=&quot;https://shirt.writethedocs.org/&quot;&gt;Write the Docs Prague 2021 Pop-Up Shop&lt;/a&gt; is still open!
We have loose and fitted options from different fabrics, and you can choose exactly the size and cut you want. The campaign will run in 3-day batches for another few weeks. Shipping is available from the USA or Europe.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;New this year&lt;/strong&gt;: You can shop for non-conference swag in our &lt;a class=&quot;reference external&quot; href=&quot;https://writethedocs.threadless.com/&quot;&gt;Write the Docs Community Shop&lt;/a&gt; on Threadless.
We have non-apparel options like stickers, notebooks, bags, and other accessories with various community slogens (including the now-famous “Docs or it didn’t happen!”).&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;code-of-conduct-transparency-report&quot;&gt;
&lt;h2&gt;Code of Conduct transparency report&lt;/h2&gt;
&lt;p&gt;As with any Write the Docs event, this conference was covered by our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/code-of-conduct/&quot;&gt;community Code of Conduct&lt;/a&gt;.
We aim to be as transparent with CoC incidents and enforcement as we can.&lt;/p&gt;
&lt;p&gt;To ensure that our CoC was visible and accessible, we took a number of specific steps:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Every participant agreed to the Code of Conduct in advance during registration.&lt;/li&gt;
&lt;li&gt;The CoC, or a summary, was included on the conference website and Hopin Reception&lt;/li&gt;
&lt;li&gt;The CoC was repeatedly mentioned in our conference introduction and announcements.&lt;/li&gt;
&lt;li&gt;We specifically stressed that the CoC applies to all conference spaces including the social event.&lt;/li&gt;
&lt;li&gt;We encouraged all attendees to report any incident, even if they were not sure whether it was a violation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;None of our organizers were approached about any CoC concerns at this event.
We know that this is, in part, a reflection of the thoughtful and inclusive community that we’re so lucky to have.&lt;/p&gt;
&lt;p&gt;That being said, we’re also very conscious of the fact that just because nothing was reported doesn’t mean nothing happened.
If there was any personal conduct or other aspect of the conference experience that did not meet the expectations of behavior set out in the CoC, please email us at &lt;a class=&quot;reference external&quot; href=&quot;mailto:conduct&amp;#37;&amp;#52;&amp;#48;writethedocs&amp;#46;org&quot;&gt;conduct&lt;span&gt;&amp;#64;&lt;/span&gt;writethedocs&lt;span&gt;&amp;#46;&lt;/span&gt;org&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;keep-in-touch&quot;&gt;
&lt;h2&gt;Keep in touch&lt;/h2&gt;
&lt;p&gt;As you probably know, we’ve decided to take a break this year from a full Australia &amp;amp; India conference, to help the organizers maintain their well-being and prevent burnout.
Instead of the conference, we’re organizing a more casual super-meetup instead. Stay tuned for details soon!&lt;/p&gt;
&lt;p&gt;We’re also looking for more sponsors to make our other events just as magical as this year’s Prague event.
You can see all our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/sponsorship/&quot;&gt;sponsorship options&lt;/a&gt; on our website.&lt;/p&gt;
&lt;p&gt;Our Slack network has expanded yet again this year.
Our #general Slack channel has been extra busy in the days and weeks leading up to the conference, and we hope that y’all continue the conversations throughout the year.
If you haven’t joined, now’s the time! Check out the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/slack/&quot;&gt;Write the Docs Slack&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/newsletter/&quot;&gt;monthly newsletter&lt;/a&gt; is the other place to keep track of everything that is happening with the community.
Subscribe to make sure you hear about all the conferences, meetups, job postings, and summaries of relevant conversations in our Slack.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;thanks-again-to-our-sponsors&quot;&gt;
&lt;h2&gt;Thanks again to our sponsors&lt;/h2&gt;
&lt;p&gt;Thanks so much to the following companies for supporting the Prague conference this year:&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.redhat.com/en&quot;&gt;Red Hat&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.people-text.de/en/home-en.html&quot;&gt;people text&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.knowledgeowl.com&quot;&gt;KnowledgeOwl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.jetbrains.com/&quot;&gt;JetBrains&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://opencollective.com/open-web-docs&quot;&gt;Open Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://aiven.io/&quot;&gt;Aiven&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://developer.mozilla.org/en-US/&quot;&gt;MDN Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/blockquote&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;until-next-time&quot;&gt;
&lt;h2&gt;Until next time&lt;/h2&gt;
&lt;p&gt;We’re so grateful to our sponsors, speakers, volunteers, and attendees for making this conference possible.
Whether you were able to attend this time or not, we hope to see you again next year and we wish everyone a safe and happy time!&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Write the Docs Newsletter – October 2021</title>
    <id>https://www.writethedocs.org/blog/newsletter-october-2021/</id>
    <updated>2021-10-05T00:00:00Z</updated>
    <published>2021-10-05T00:00:00Z</published>
    <link href="https://www.writethedocs.org/blog/newsletter-october-2021/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;write-the-docs-newsletter-october-2021&quot;&gt;

&lt;p&gt;Hello everyone!&lt;/p&gt;
&lt;p&gt;It’s Beth here, writing while I’m listening in to Write the Docs Prague. I hope everyone who attended had a great time! For those of you who couldn’t make it, keep an eye out: we’ll be publishing the talk videos on YouTube fairly soon. And if you’d like to get more of a flavour of the conference, you can listen to &lt;a class=&quot;reference external&quot; href=&quot;https://missmikeymay.com/&quot;&gt;the intermission music&lt;/a&gt; - which I am bopping along to as I type :D&lt;/p&gt;
&lt;p&gt;And one more thing to keep your eyes peeled for - the Salary Survey is going through its finishing touches. We’re really excited to be continuing this work to improve transparency around documentarian salaries, so watch this space!&lt;/p&gt;
&lt;p&gt;In the meantime, we’ve had another month of interesting conversations and insights from the Write the Docs Slack. Read on, and enjoy!&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;docs-review-strategies-for-lone-writers&quot;&gt;
&lt;h2&gt;Docs review strategies for lone writers&lt;/h2&gt;
&lt;p&gt;Being a company’s only technical writer comes with advantages and disadvantages, but a common challenge for lone writers is getting reviews for documentation. When there’s no established docs review process and there are no other documentarians to turn to, here are some strategies the lone writers of Write the Docs use to get the work done.&lt;/p&gt;
&lt;p&gt;You may be able to publish your best efforts without review and await (or seek) corrections, whether from users or others at your company. Docs have bugs just like code, and speedy fixes may be more within your control. The downside with this approach is any mistakes are public until you fix them.&lt;/p&gt;
&lt;p&gt;The fastest way to get corrections may be to publish errors, but sometimes that’s not an option. In this case, try to assemble an informal group of docs review resources. Seek a product manager or subject matter expert to review docs for accuracy. For readability, look for someone else whose job requires writing, perhaps in marketing or communications. Your experiments here could help drive support for a more formal docs review process.&lt;/p&gt;
&lt;p&gt;Some lone writers solicit docs review by creating feedback channels in Slack with the &lt;a class=&quot;reference external&quot; href=&quot;https://slack.com/help/articles/360035692513-Guide-to-Workflow-Builder&quot;&gt;Workflow Builder&lt;/a&gt;. For example, you could create a #documentation channel with a built-in form for submitting correction requests, with fields for specifying the page in question and the requested corrections. Then the Slackbot can notify you when someone submits a correction.&lt;/p&gt;
&lt;p&gt;For detailed instructions for setting up your own docs feedback workflow in Slack and other insights from this discussion, read Darryl J. White’s blog post &lt;a class=&quot;reference external&quot; href=&quot;https://www.djw.fyi/posts/editing-and-gathering-feedback/&quot;&gt;Editing and Gathering Feedback&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;equipment-you-find-useful-for-working-remotely&quot;&gt;
&lt;h2&gt;Equipment you find useful for working remotely&lt;/h2&gt;
&lt;p&gt;What are the most useful tools for working from home? This question sparked a lot of conversations this month, but top of everyone’s list was multiple monitors. The simple ability to see more than one thing at a time is hugely helpful, and the benefits of improved productivity and less window-switching have made them essential for work-from-home life.&lt;/p&gt;
&lt;p&gt;Other recommended tools mentioned were sit-stand desks and computer accessories like comfortable wire-free mice and keyboards. Aside from hardware tools, software applications like &lt;a class=&quot;reference external&quot; href=&quot;https://www.grammarly.com/&quot;&gt;Grammarly&lt;/a&gt;, macOS’s Voice Memos, and &lt;a class=&quot;reference external&quot; href=&quot;https://apps.apple.com/us/app/bettersnaptool/id417375580?mt=12&quot;&gt;BetterSnapTool&lt;/a&gt; proved beneficial for working from home. Even traditional tools, like a whiteboard and pen and paper, were brought up.&lt;/p&gt;
&lt;p&gt;With so many software and hardware tools available, it can be challenging to pick the ones that are worth putting in the metaphorical “toolbelt.” However, whether you want to be more organized or keep track of important meetings, there is always the right tool for the remote job.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;what-s-in-a-documentarian-resume-anyway&quot;&gt;
&lt;h2&gt;What’s in a documentarian resume anyway?&lt;/h2&gt;
&lt;p&gt;As anyone who spends much time around the Write the Docs community knows, the questions around just who writes the docs, what their job titles might be, what their skills and experience might be, have no single definitive answer. One of our longest recent threads about job descriptions and resumes explored a number of possible answers, though. Here’s what we took away from the 100+ message thread:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Writers and hiring managers alike struggle with whether to focus on docs-specific skills – writing, tools, workflows – or on specific technologies in search of docs. Folks seemed to agree, though, that a documentation position that requires familiarity with the specific tech to be documented needs to emphasize required skills. And finding just the right fit is a challenge whether you’re hiring or looking to get hired.&lt;/li&gt;
&lt;li&gt;Writers with non-writing backgrounds can prefer not to list specific tech on their resumes, especially coding, for fear they’ll be considered overqualified or otherwise not the right fit. Other writers are reluctant to mention specific tech if they’re not experts, for fear their skills will be challenged, or assumed to be greater than the writer feels they are.&lt;/li&gt;
&lt;li&gt;Some writers emphasize their ability to learn new tech – they consider themselves generalists with strong research skills and experience picking up new areas sufficiently to be able to document them well. Others emphasize their skills in specific technical areas – they consider themselves specialists with the ability to take on non-writer work as needed, especially in QA, design, UX, or support. Curiosity and eagerness to explore and learn were attributes everyone seemed to agree are vital, whichever approach you choose.&lt;/li&gt;
&lt;li&gt;Job seekers: be thoughtful about what you put on your resume, don’t rely on LinkedIn alone, and try to tailor your job searches to companies you think might be a good fit for what you want to do – whether it’s tech you want to learn, tech you know a little about, or tech you know a lot about. Cover letters can help you show how you fit a job listing, beyond what you put in your resume.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you’re interested in pursuing the conversation, join us over at &lt;a class=&quot;reference external&quot; href=&quot;https://github.com/writethedocs/www/discussions/1596/&quot;&gt;the GitHub Discussion&lt;/a&gt; one stalwart WTDer started. Carry on, folks!&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;what-were-reading-and-listening-to&quot;&gt;
&lt;h2&gt;What we’re reading and listening to&lt;/h2&gt;
&lt;p&gt;The #bipoc group’s been discussing the following materials on diversity, inclusion, and equity. Want to join the conversation? Please join us in the &lt;a class=&quot;reference external&quot; href=&quot;https://app.slack.com/client/T0299N2DL/C016STMEWJD&quot;&gt;#bipoc Slack channel&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;In the United States &lt;a class=&quot;reference external&quot; href=&quot;https://www.hispanicheritagemonth.gov/&quot;&gt;it’s Hispanic Heritage month&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A short read: From Courageous Conversation, &lt;a class=&quot;reference external&quot; href=&quot;https://courageousconversation.com/the-difference-between-hispanic-and-latino/&quot;&gt;do you know the difference between Hispanic and Latino&lt;/a&gt;?&lt;/p&gt;
&lt;p&gt;A longer listen: From MPR news, &lt;a class=&quot;reference external&quot; href=&quot;https://www.mprnews.org/amp/episode/2021/07/13/bipoc-latinx-poc-how-we-do-and-dont-identify-and-why&quot;&gt;How the term Latinx, and other labels, miss the mark&lt;/a&gt;. This episode talks about labels such as Latinx, BIPOC, etc, and explores where they started, what they mean, and who uses them.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;featured-job-posts&quot;&gt;
&lt;h2&gt;Featured job posts&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/513/mdn-senior-community-manager-1-year-fixed-term/&quot;&gt;MDN Senior Community Manager (1-year fixed term)&lt;/a&gt;, MDN (remote - Germany)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/512/mdn-senior-technical-writer-1-year-fixed-term/&quot;&gt;MDN Senior Technical Writer (1-year fixed term)&lt;/a&gt;, MDN (remote - Germany)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/511/programming-writer/&quot;&gt;Programming Writer&lt;/a&gt;, DigitalOcean (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/502/technical-writer-intellij-idea/&quot;&gt;Technical Writer (IntelliJ IDEA)&lt;/a&gt;, JetBrains (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/504/developer-educator/&quot;&gt;Developer Educator&lt;/a&gt;, Aiven (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/503/technical-writer-youtrack/&quot;&gt;Technical Writer (YouTrack)&lt;/a&gt;, JetBrains (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/506/technical-writer/&quot;&gt;Technical Writer&lt;/a&gt;, Inductive Automation (remote - US)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/508/technical-writer/&quot;&gt;Technical Writer&lt;/a&gt;, Aiven (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/485/technical-writer/&quot;&gt;Technical Writer&lt;/a&gt;, Entado (remote - US)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;To apply for these jobs and more, visit the&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/&quot;&gt;Write the Docs job board&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;virtual-events-coming-up&quot;&gt;
&lt;h2&gt;Virtual events coming up&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;11 October, 19:30 IDT (Israel) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-The-Docs-TAplus/events/280730503/&quot;&gt;Python for Documentarians&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;12 October, 08:30 EDT (USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/ne-write-the-docs/events/hqvdfsyccnbqb/&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;13 October, 12:00 AEDT (Australia) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Australia/events/280353337/&quot;&gt;Findability in the world of docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;21 October, 19:00 PDT (USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Bay-Area/events/281038631/&quot;&gt;Roundtable: New to the field!&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;21 October, 19:00 EDT (Canada) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Toronto/events/280155584&quot;&gt;Write the Docs Toronto&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;26 October, 08:30 EDT (USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/ne-write-the-docs/events/hqvdfsyccnbjc/&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Get Ready for the Conference!</title>
    <id>https://www.writethedocs.org/conf/prague/2021/news/get-ready/</id>
    <updated>2021-09-28T00:00:00Z</updated>
    <published>2021-09-28T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/prague/2021/news/get-ready/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;get-ready-for-the-conference&quot;&gt;

&lt;p&gt;Hey everyone!&lt;/p&gt;
&lt;p&gt;We’re just a few days away from the start of the conference, and we’re getting excited to see you soon at our online venue for three days of content, collaboration, and conversation. We’re happy to share with you some useful resources to help you prepare for the conference.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;tickets-sales-closing-on-thursday-september-30th&quot;&gt;
&lt;h2&gt;Tickets sales closing on Thursday, September 30th&lt;/h2&gt;
&lt;p&gt;We wanted to let you know that we will be closing ticket sales on &lt;strong&gt;Thursday, September 30th at 20:00 CEST&lt;/strong&gt;. This helps the organizer team manage the platform registrations in time for the start of the conference, and helps keep the cozy community feeling of the event.&lt;/p&gt;
&lt;p&gt;If you were hoping to come to this years event, we recommend that you &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/tickets/&quot;&gt;get your tickets before Thursday&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;If you already purchased a ticket you should have received an email from us with your Hopin registration link.&lt;/strong&gt; After we close ticket sales, we will send another email to everyone with a reminder and a link to access the Hopin event.&lt;/p&gt;
&lt;p&gt;The Hopin access links were sent today to all Ti.to ticket holders, so check your inbox for a message. If you don’t get an email from us by the end of the week, please check your spam/junk folder first, and then email us and we’ll help you out.&lt;/p&gt;
&lt;p&gt;After you register in Hopin and set up your profile, you will be ready to get started on Sunday morning with the Writing Day!&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;welcome-wagon-guide-and-orientation-sessions&quot;&gt;
&lt;h2&gt;Welcome Wagon guide and orientation sessions&lt;/h2&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/welcome-wagon/&quot;&gt;Welcome Wagon guide&lt;/a&gt; has been updated to help you get the most out of our event this year.&lt;/p&gt;
&lt;p&gt;We have a lot of information about how to use Hopin, as well as lots of tips and tricks for the best way to plan your days.&lt;/p&gt;
&lt;p&gt;This year we are also happy to announce that the Welcome Wagon team will hold &lt;strong&gt;live orientation sessions&lt;/strong&gt; for the virtual platform! The sessions will be held on Sunday during Writing Day and on Monday morning before the conference introduction talk. These sessions will give you a chance to walk through the virtual event and ask all your questions.&lt;/p&gt;
&lt;p&gt;Check out the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/schedule/&quot;&gt;Schedule page&lt;/a&gt; for exact time and location.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;all-our-events-and-activities&quot;&gt;
&lt;h2&gt;All our events and activities&lt;/h2&gt;
&lt;p&gt;Write the Docs is more than a conference. Every year we make sure to have a variety of activities that our attendees can enjoy, whether you want to learn something, meet new people, or share knowledge. And even though this years conference is held online, we’re holding to that plan.&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;strong&gt;Lightning Talks.&lt;/strong&gt; We’ll have &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/lightning-talks/&quot;&gt;lightning talks&lt;/a&gt; each day after lunch. These are 5 minute presentations and a lot of fun. They can be about anything you want, this is your chance to share something you are passionate about with the audience. Slides are not required. Sign-up for lightning talks will be posted on Monday and Tuesday morning, and the selected talks will be announced before the lunch break on each day.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unconference.&lt;/strong&gt; We’ll be running the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/unconference/&quot;&gt;Unconference&lt;/a&gt; all day Monday and on Tuesday afternoon. Want to chat with like-minded folks about a specific thing? This is the place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Job Fair&lt;/strong&gt;. As with the previous years, on Tuesday morning we’ll have a &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/job-fair&quot;&gt;job fair&lt;/a&gt; where you can find your next documentarian friendly job.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Social event&lt;/strong&gt;. On Monday night the main stage will be closed, and we will switch to social mode! We will be using a spatial chat platform for the social event this year, and we will post the link for the social space during the day on Monday. It will be much closer to a “real life” social where attendees can move between different rooms and group conversations, and the &lt;a class=&quot;reference external&quot; href=&quot;https://www.ericholscher.com/blog/2017/aug/2/pacman-rule-conferences/&quot;&gt;Pac-Man Rule&lt;/a&gt; even works!&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conference Help Desk&lt;/strong&gt;. If you have any questions about navigating the virtual event, we’ll be running the Write the Docs Helpdesk booth, where you can chat with one of the organizers and the Welcome Wagon team.&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&quot;system-message&quot;&gt;
&lt;p class=&quot;system-message-title&quot;&gt;System Message: INFO/1 (&lt;tt class=&quot;docutils&quot;&gt;/home/docs/checkouts/readthedocs.org/user_builds/www-zh/checkouts/latest/docs/conf/prague/2021/news/get-ready.rst&lt;/tt&gt;, line 7); &lt;em&gt;&lt;a href=&quot;#id1&quot;&gt;backlink&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
Duplicate explicit target name: “schedule page”.&lt;/div&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/schedule/&quot;&gt;Schedule page&lt;/a&gt; has the latest and most complete information about all our events. This is where we will also update any changes/cancellations if they should occur.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;thanks-so-much-to-all-our-sponsors&quot;&gt;
&lt;h2&gt;Thanks so much to all our sponsors&lt;/h2&gt;
&lt;p&gt;We are so grateful to have our sponsors help in bringing these events to life every year.
You’ll be able to chat with most of our sponsors at the Job Fair, and a few will have booths for conversations the entire conference.&lt;/p&gt;
&lt;p&gt;Thanks so much to the following companies for supporting the Portland conference this year:&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.redhat.com/en&quot;&gt;Red Hat&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.people-text.de/en/home-en.html&quot;&gt;people text&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.knowledgeowl.com&quot;&gt;KnowledgeOwl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.jetbrains.com/&quot;&gt;JetBrains&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://opencollective.com/open-web-docs&quot;&gt;Open Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://aiven.io/&quot;&gt;Aiven&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://developer.mozilla.org/en-US/&quot;&gt;MDN Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/blockquote&gt;
&lt;p&gt;We’re excited to see all of you soon,
and can’t wait to share a wonderful few days with you in our online space.&lt;/p&gt;
&lt;p&gt;The Write the Docs team&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Announcing Full Schedule</title>
    <id>https://www.writethedocs.org/conf/prague/2021/news/announcing-schedule/</id>
    <updated>2021-09-08T00:00:00Z</updated>
    <published>2021-09-08T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/prague/2021/news/announcing-schedule/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;announcing-full-schedule&quot;&gt;

&lt;p&gt;Hey everyone!&lt;/p&gt;
&lt;p&gt;We’re less than a month away from the second online Prague conference, and we’re working hard to make sure it’ll be as welcoming and as fun as last year’s event.&lt;/p&gt;
&lt;p&gt;Today we’re announcing the full presentation schedule and the platform we’ll be hosting the conference on.
We are working on last-minute details for a few more activities during the conference, so look out for more information in our next mailing.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;conference-platform&quot;&gt;
&lt;h2&gt;Conference platform&lt;/h2&gt;
&lt;p&gt;The conference will again be held on &lt;a class=&quot;reference external&quot; href=&quot;https://hopin.to/&quot;&gt;https://hopin.to/&lt;/a&gt;, which not only provides a stage for our amazing speakers, but also has integrated chat, unconference rooms with breakout calls, expo booths, and even a virtual hallway. We have an updated &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/welcome-wagon/&quot;&gt;Welcome Wagon&lt;/a&gt; guide to help you get familiar with the platform before you’ve even arrived.&lt;/p&gt;
&lt;p&gt;IMPORTANT: If you registered for a ticket on Ti.to, please monitor your inboxes during the next weeks for an email with a registration link to Hopin. We recommend that you register for the platform in advance, to avoid the “Monday morning rush”.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;full-presentation-schedule&quot;&gt;
&lt;h2&gt;Full presentation schedule&lt;/h2&gt;
&lt;p&gt;The conference website is now updated with the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/schedule/&quot;&gt;talk schedule&lt;/a&gt; for the main stage presentations, so you can start planning your time (and getting excited!) for the conference. We’re excited to have live Q&amp;amp;A after most talks, which will come from your questions but be moderated by an MC.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;start-thinking-about-writing-day&quot;&gt;
&lt;h2&gt;Start thinking about Writing Day&lt;/h2&gt;
&lt;p&gt;Our pre-conference &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/writing-day/&quot;&gt;Writing Day&lt;/a&gt; will happen on Sunday, and it is much more fun when folks come with their own projects in mind!&lt;/p&gt;
&lt;p&gt;If you have a project or are part of a community that you think would benefit from a writing sprint, start brainstorming now about what you might want to focus on.
If you’d like us to include your project on the Writing Day page, drop us an email at &lt;a class=&quot;reference external&quot; href=&quot;mailto:prague&amp;#37;&amp;#52;&amp;#48;writethedocs&amp;#46;org&quot;&gt;prague&lt;span&gt;&amp;#64;&lt;/span&gt;writethedocs&lt;span&gt;&amp;#46;&lt;/span&gt;org&lt;/a&gt;.
Or just show up on Sunday ready to introduce your project!&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;shirts-still-on-sale&quot;&gt;
&lt;h2&gt;Shirts still on sale&lt;/h2&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://shirt.writethedocs.org/&quot;&gt;Write the Docs Prague 2021 Pop-Up Shop&lt;/a&gt; is open! We have loose and fitted options from different fabrics, and you can choose exactly the size and cut you want.&lt;/p&gt;
&lt;p&gt;The campaign will run in 3-day batches until November 30th. Shipping is available from the USA or Europe. However, due to the global shipping situation, we recommend you order your shirt at least 2-3 weeks in advance if you want to wear your new shirt during the conference.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;all-conference-events-and-activities&quot;&gt;
&lt;h2&gt;All conference events and activities&lt;/h2&gt;
&lt;p&gt;Write the Docs is more than a conference. Every year we make sure to have a variety of activities that our attendees can enjoy, whether you want to learn something, meet new people, or share knowledge. And even though this years conference is held online, we’re holding to that plan.&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;strong&gt;Lightning Talks.&lt;/strong&gt; We’ll have &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/lightning-talks/&quot;&gt;lightning talks&lt;/a&gt; each day after lunch. These are 5 minute presentations and a lot of fun. They can be about anything you want, this is your chance to share something you are passionate about with the audience. Slides are not required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unconference.&lt;/strong&gt; We’ll be running the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/unconference/&quot;&gt;Unconference&lt;/a&gt; all day Monday and on Tuesday afternoon. Want to chat with like-minded folks about a specific thing? This is the place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Job Fair&lt;/strong&gt;. As with the previous few years, on Tuesday morning we’ll have a &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/job-fair&quot;&gt;job fair&lt;/a&gt; where you can find your next documentarian friendly job.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Social event&lt;/strong&gt;. On Monday night, the main stage will be closed and the focus will be on attendee-created sessions. You’re welcome to create sessions for board games, trivia quizzes, karaoke, or any other social activity that you want to share with your fellow documentarians.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conference Help Desk&lt;/strong&gt;. If you have any questions about navigating the virtual event, we’ll be running the Write the Docs Helpdesk booth, where you can chat with one of the organizers and the Welcome Wagon team.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/schedule/&quot;&gt;Schedule page&lt;/a&gt; has the latest and most complete information about all our events. This is where we will also update any changes/cancellations if they should occur.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;thanks-to-our-sponsors&quot;&gt;
&lt;h2&gt;Thanks to our sponsors&lt;/h2&gt;
&lt;p&gt;We are so grateful to have our sponsors help in bringing these events to life every year. Thanks sincerely to the following companies for supporting the Write the Docs community:&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.redhat.com/en&quot;&gt;Red Hat&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.people-text.de/en/home-en.html&quot;&gt;people text&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.knowledgeowl.com&quot;&gt;KnowledgeOwl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.jetbrains.com/&quot;&gt;JetBrains&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://opencollective.com/open-web-docs&quot;&gt;Open Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://aiven.io/&quot;&gt;Aiven&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://developer.mozilla.org/en-US/&quot;&gt;MDN Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/blockquote&gt;
&lt;p&gt;Head over to our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2020/sponsors/prospectus/&quot;&gt;sponsorship prospectus&lt;/a&gt; for details on how your company can get involved!
We have several types of sponsorship available, including tables at the job fair that we’ll be hosting on Tuesday.&lt;/p&gt;
&lt;p&gt;Thanks so much for all your support and enthusiasm so far – we’re so excited to see you all next month!&lt;/p&gt;
&lt;p&gt;The Write the Docs team&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Write the Docs Newsletter – September 2021</title>
    <id>https://www.writethedocs.org/blog/newsletter-september-2021/</id>
    <updated>2021-09-07T00:00:00Z</updated>
    <published>2021-09-07T00:00:00Z</published>
    <link href="https://www.writethedocs.org/blog/newsletter-september-2021/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;write-the-docs-newsletter-september-2021&quot;&gt;

&lt;p&gt;Hi everyone! Back from our summer break, it’s Beth and the newsletter team, bringing you our edition for September.&lt;/p&gt;
&lt;p&gt;September already? I know, the year is flowing by. Autumn is slowly but surely arriving here in Europe; and while the weather may be cooling, at Write the Docs we’re warming up for our second virtual conference for the year. “Prague” is coming up on 3rd-5th October; our fabulous &lt;a class=&quot;reference external&quot; href=&quot;/conf/prague/2021/news/announcing-speakers/&quot;&gt;speakers&lt;/a&gt; have been announced, and &lt;a class=&quot;reference external&quot; href=&quot;/conf/prague/2021/tickets/&quot;&gt;ticket sales&lt;/a&gt; are still open. Hope to see you there!&lt;/p&gt;
&lt;p&gt;Sadly, that will also be our last conference of the year: the Australia and India conference has been &lt;a class=&quot;reference external&quot; href=&quot;/conf/australia/2021/news/cancel-announcement/&quot;&gt;cancelled&lt;/a&gt;. Bearing in mind the immense stress of the past year and a half, we’re instead planning a smaller event to be more manageable for the organizing team. It’ll be in a meetup format, but with some of the great speakers planned for the conference - keep your eyes peeled for announcements there.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;avoiding-the-dreaded-wall-of-text&quot;&gt;
&lt;h2&gt;Avoiding the dreaded “wall of text”&lt;/h2&gt;
&lt;p&gt;The “wall of text” is a familiar conundrum for many documentarians, especially when a topic requires in-depth explanation. As writers and as readers ourselves, we want docs that provide sufficient detail and are skimmable at the same time. Here are some strategies that go beyond surface-level fixes to also add helpful context and support a better user experience:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Add thoughtful headings and subheadings to provide content signposts and help readers find information they might otherwise miss in a long span of text. Meaningful headings do more than just break up the text - they provide a mental picture of everything on the page and allow readers to focus on the pieces they really need to understand.&lt;/li&gt;
&lt;li&gt;Use progressive disclosure, like linking to secondary pages for details or using expandable panels, to keep the entire text available without overwhelming readers at first glance. Learn more about progressive disclosure from this 2017 Write the Docs Portland talk, &lt;a class=&quot;reference external&quot; href=&quot;/videos/na/2017/building-navigation-for-your-doc-site-5-best-practices-tom-johnson/&quot;&gt;Building navigation for your doc site: 5 best practices&lt;/a&gt;, by Tom Johnson.&lt;/li&gt;
&lt;li&gt;Rewrite long paragraphs to use lists. Condense the most critical points to eye-catching items in a list and make the text more skimmable. Write instructions in individually numbered steps.&lt;/li&gt;
&lt;li&gt;Look for opportunities to use formatting to add meaning to the text. Use special icons or different background shading to delineate notes and warnings. Put code snippets, quotations, and math equations in their own indented blocks. Use bold font weight to make keywords stand out. Left-justify the first paragraph for each topic and block-indent subsequent paragraphs on the same topic.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;where-are-all-the-junior-positions&quot;&gt;
&lt;h2&gt;Where are all the junior positions?&lt;/h2&gt;
&lt;p&gt;An interesting topic circulating in the WTD community is the scarcity of entry-level technical writing jobs. Nowadays, most employers seem to be looking for writers with at least five years of experience. But why is that the case? Perhaps because teams need the help of a seasoned writer to help them grow, but also because, in most situations, an experienced writer provides a greater return on investment than a junior writer. If a team is overloaded, they might feel unable to give someone less experienced the training, guidance, and mentorship they need.&lt;/p&gt;
&lt;p&gt;So, how can junior writers find jobs when it feels like the odds are stacked against them? One suggestion is to pick a niche and dig into it. By becoming proficient in a specialized subject, new writers will be better equipped to compete in the job market - as other candidates for entry-level tech writing roles can be engineers or support engineers wanting to transfer into writing-oriented roles.&lt;/p&gt;
&lt;p&gt;Another approach is to tap into your professional network. In a saturated industry, knowing someone who can help you get more experience on your resume can help hugely. After gaining some experience, seeking new positions becomes much easier - though that doesn’t mean it won’t be challenging still.&lt;/p&gt;
&lt;p&gt;The best advice for those interested in tech writing, regardless of the industry, is to establish domain knowledge in a subject, leverage professional networks, create a portfolio of work, and explore opportunities that allow for continuous learning and skill building to achieve a fulfilling career. For more information on starting a tech writer career, check out &lt;a class=&quot;reference external&quot; href=&quot;https://www.careerexplorer.com/careers/technical-writer/how-to-become/&quot;&gt;this article on Career Explorer&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;the-basics-you-need-to-document-an-api&quot;&gt;
&lt;h2&gt;The basics you need to document an API&lt;/h2&gt;
&lt;p&gt;In a discussion this month around demystifying API documentation, we asked: what’s the minimum that you need to know to document an API? Here’s what the community thought:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;What the user needs to know (just like any other documentation!). For APIs, that includes descriptions of all of the parameters, a sample request and response, as well as information about authenticating.&lt;/li&gt;
&lt;li&gt;How to write and send cURL requests.&lt;/li&gt;
&lt;li&gt;The principles of RESTful APIs, including the “verbs”: Create (POST), Read (GET), Update (PUT), and Delete (DELETE).&lt;/li&gt;
&lt;li&gt;Most agreed that understanding the purpose of YAML and JSON is helpful; learning to read them is usually fairly straightforward.&lt;/li&gt;
&lt;li&gt;Do you need to know the coding language used to create the API? Not necessarily. Having some programming knowledge is helpful, but if you have tools that can call endpoints and can give you reliable information for payloads and responses, you don’t need to know the language. Similarly, if you have great programmers that document the code, you may just need to understand the code’s structure well enough to find information.&lt;/li&gt;
&lt;li&gt;What about the OpenAPI spec (formerly Swagger)? Not necessarily. It’s useful you want to define the API, but not necessary if you’re just helping the developers document it - you’ll mostly learn it along the way. (There are also a couple of other formats, like RAML.)&lt;/li&gt;
&lt;li&gt;Finally, it’s helpful to have some understanding of how software communicates over HTTP: headers, errors, bodies. Some notions of computer security and performance - which isn’t too far away from pretending your day-to-day use of passwords and problems with connectivity issues. One handy tip - “imagine you’re a browser”!&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;documenting-hardware-different-from-software&quot;&gt;
&lt;h2&gt;Documenting hardware: different from software?&lt;/h2&gt;
&lt;p&gt;An inquiry about how hardware documentation might be different from software (or not!) produced a range of comparisons and stories. Spoiler alert: yes indeed it can be different, but “hardware” is a broad term! Contributors mentioned vertical farming equipment, hardware for biometric-based security systems, products for work safety and firefighting, heating appliances, and wind turbines.&lt;/p&gt;
&lt;p&gt;One big challenge for everyone who described documenting hardware is the inability to test the product – either test it at all, test it readily, or test it in anything like a real-world scenario. Every hardware documentarian who replied noted their greater dependence on test teams, engineering, or technical support.&lt;/p&gt;
&lt;p&gt;Some hardware products must be produced to exacting specifications, which can extend to the documentation, so depending on the product, doc reviews are more rigorous. PDFs and print manuals are much more common, and producing them to specification more exacting. Proofreading matters differently when fixing a mistake requires redoing print proofs! Plus, illustrations can matter more, to the point where one contributor likened themselves to a part-time art director.&lt;/p&gt;
&lt;p&gt;Finally, there’s rarely any opportunity to gather customer feedback for the docs. Several folks missed the engagement with a developer audience their software docs work gave them, and the challenges of documenting new software features. They also acknowledged, though, that the challenge of setting up a doc system can be similar.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;what-were-reading-and-learning&quot;&gt;
&lt;h2&gt;What we’re reading and learning&lt;/h2&gt;
&lt;p&gt;The #bipoc group’s been discussing the following materials on diversity, inclusion, and equity. Want to join the conversation? Please join us in the &lt;a class=&quot;reference external&quot; href=&quot;https://app.slack.com/client/T0299N2DL/C016STMEWJD&quot;&gt;#bipoc Slack channel&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Two short reads: &lt;a class=&quot;reference external&quot; href=&quot;https://techbullion.com/the-differences-between-diversity-and-inclusion-in-the-workplace/&quot;&gt;This article&lt;/a&gt; on TechBullion discusses the differences between diversity and inclusion in the workplace and why businesses need both. Many places lump these two terms together, but they are in fact two different things. And &lt;a class=&quot;reference external&quot; href=&quot;https://www.wellright.com/blog/bipoc-emotional-wellness-diverse-inclusive-workplace&quot;&gt;this article&lt;/a&gt; on WellRight expands on the topic of inclusion and discusses what it means to create a diverse and inclusive workplace. Hint, it goes beyond hiring.&lt;/p&gt;
&lt;p&gt;A medium-length read: After the death of Daunte Wright, &lt;a class=&quot;reference external&quot; href=&quot;https://hypebae.com/2020/6/mental-health-resources-poc-black-minorities-community-racism-george-floyd&quot;&gt;this post&lt;/a&gt; on HYPEBAE hosted a list of mental health resources for Black and other POCs. However, mental health isn’t a one-time need or a resource that should be overlooked; these resources are still available.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;from-our-sponsor&quot;&gt;
&lt;h2&gt;From our sponsor&lt;/h2&gt;
&lt;p&gt;This month’s newsletter is sponsored by Scroll Viewport:&lt;/p&gt;
&lt;hr&gt;
&lt;table width=&quot;100%&quot; border=&quot;0&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; style=&quot;width:100%; max-width: 600px;&quot;&gt;
  &lt;tbody&gt;
    &lt;tr&gt;
      &lt;td width=&quot;75%&quot;&gt;
          &lt;p&gt;
          You and your team pour your heart and soul into your product documentation, so give it the online platform it deserves! Your customers will thank you for it.
          &lt;/p&gt;&lt;p&gt;
          Publish your docs as a branded help center so your users can self-serve the help they need.
          &lt;/p&gt;&lt;p&gt;
          Got 5 minutes? That's all you need to &lt;a href=&quot;http://scroll-viewport.io/?utm_source=write-the-docs&amp;utm_medium=email&amp;utm_campaign=2108-vprt-lp&amp;utm_content=september-newsletter&quot;&gt;get started →&lt;/a&gt;
          &lt;/p&gt;
      &lt;/td&gt;
      &lt;td width=&quot;25%&quot;&gt;
        &lt;a href=&quot;https://scroll-viewport.io/?utm_source=write-the-docs&amp;utm_medium=email&amp;utm_campaign=2108-vprt-lp&amp;utm_content=september-newsletter&quot;&gt;
          &lt;img style=&quot;margin-left: 15px;&quot; alt=&quot;Scroll Viewport&quot; src=&quot;/_static/img/sponsors/scroll-viewport.png&quot;&gt;
        &lt;/a&gt;
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;
&lt;hr&gt;&lt;p&gt;&lt;em&gt;Interested in sponsoring the newsletter? Take a look at our&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;/sponsorship/newsletter/&quot;&gt;sponsorship prospectus&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;featured-job-posts&quot;&gt;
&lt;h2&gt;Featured job posts&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/464/api-technical-writer/&quot;&gt;API Technical Writer&lt;/a&gt;, Banyan Security (remote)&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/476/product-manager-technical-documentation-lead/&quot;&gt;Product Manager: Technical Documentation Lead&lt;/a&gt;, Recursion Pharmaceuticals&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/job/343/technical-writer/&quot;&gt;Technical Writer&lt;/a&gt;, Instabase (San Francisco)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;To apply for these jobs and more, visit the&lt;/em&gt; &lt;a class=&quot;reference external&quot; href=&quot;https://jobs.writethedocs.org/&quot;&gt;Write the Docs job board&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;virtual-events-coming-up&quot;&gt;
&lt;h2&gt;Virtual events coming up&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;14 September, 8:30am ET (New England, USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/ne-write-the-docs/events/hqvdfsyccmbsb/&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;14 September, 7pm MDT (Calgary, Canada) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/wtd-calgary/events/280407966/&quot;&gt;September 2021 Write the Docs Calgary Meetup&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;23 September, 7pm PDT (West Coast, USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/virtual-write-the-docs-west-coast-quorum/events/280521286/&quot;&gt;More Than Words: An Introduction to Information Architecture&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;28 September, 8:30am ET (New England, USA) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/ne-write-the-docs/events/hqvdfsyccmblc/&quot;&gt;Morning social&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;13 October, 12pm AEDT (Australia) - &lt;a class=&quot;reference external&quot; href=&quot;https://www.meetup.com/Write-the-Docs-Australia/events/280353337/&quot;&gt;Findability in the world of docs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Cancelling WTD Australia and India 2021 conference</title>
    <id>https://www.writethedocs.org/conf/australia/2021/news/cancel-announcement/</id>
    <updated>2021-08-25T00:00:00Z</updated>
    <published>2021-08-25T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/australia/2021/news/cancel-announcement/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;cancelling-wtd-australia-and-india-2021-conference&quot;&gt;

&lt;p&gt;G’day folks. We’re writing to let you know that we have decided to cancel our WTD Australia and India conference for 2021.
This has been an extremely difficult decision, but we recognise the immense mental fatigue that the pandemic in general and lockdowns specifically have caused in Australia and India this year.&lt;/p&gt;
&lt;p&gt;While the community engagement and support have been fantastic across our remote meetup events and last year’s conference, we all felt stressed and burnt-out at various times during the last couple of years.
Keeping in mind the long(er)-term health of the community, we have decided to do something else in place of the conference, in a smaller scope that will be more manageable to the organizing team while still providing some continuity to the community.&lt;/p&gt;
&lt;p&gt;Here’s what we will do instead.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;super-meetup&quot;&gt;
&lt;h2&gt;Super meetup&lt;/h2&gt;
&lt;p&gt;In place of a full 2-day conference, we will select 4 talks (from the CFP process, pending confirmation from the speakers) and invite these documentarians to present their talks at a super 2-hour meetup (date &lt;strong&gt;TBA&lt;/strong&gt;).
We value the time and effort our documentarians put in to submit talk proposals and wanted to use this time to share their experience and knowledge.&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;This meetup event will be a free and open event without prior registration, so you can join in from anywhere. We will try and keep this in a timezone convenient for both our WTD Australia and India communities.&lt;/li&gt;
&lt;li&gt;We will be using the WTD Australia and India Meetup groups to announce the date for this, along with the relevant WTD Slack channels and other social media.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;time-to-recover&quot;&gt;
&lt;h2&gt;Time to recover&lt;/h2&gt;
&lt;p&gt;2021 has been a great year with our remote meetup events in Australia.
We hope you take this time to recover and refresh yourselves mentally and physically.
We will be back in 2022 with the conference (onsite hopefully!).&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;some-conference-housekeeping&quot;&gt;
&lt;h2&gt;Some conference housekeeping&lt;/h2&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;If you already registered a ticket for the conference, we will refund these promptly and in full, without cancellation fees.&lt;/li&gt;
&lt;li&gt;If you had blocked these dates in your calendar, we will try and organise the super meetup on one of these days, so that you do not have to take additional time off from work.&lt;/li&gt;
&lt;li&gt;For those who submitted a talk proposal, we thank you greatly and invite you to resubmit your talks for our conferences (Portland, Prague, Australia/India) next year. If we have selected your talk for the super meetup, we will contact you within the next two weeks.&lt;/li&gt;
&lt;li&gt;We will be closing the CFP process before the weekend, cancel future ticket sales, and publish this announcement on the conference website, along with the relevant Write the Docs Slack channels and other social media.&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;other-conferences-and-activities&quot;&gt;
&lt;h2&gt;Other conferences and activities&lt;/h2&gt;
&lt;p&gt;This announcement &lt;strong&gt;does not&lt;/strong&gt; affect any of our other conferences and activities.
Our Prague 2021 virtual conference will still take place as planned. Tickets are currently on sale, and we plan to announce the schedule soon.&lt;/p&gt;
&lt;p&gt;Stay safe and we hope to see you next year!&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Call for Proposals Extended</title>
    <id>https://www.writethedocs.org/conf/australia/2021/news/cfp-extend/</id>
    <updated>2021-08-16T00:00:00Z</updated>
    <published>2021-08-16T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/australia/2021/news/cfp-extend/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;call-for-proposals-extended&quot;&gt;

&lt;p&gt;Greetings fellow documentarians!&lt;/p&gt;
&lt;p&gt;The conference is now just under four months away, and we hope you’re already planning for this year’s remote installment of Write the Docs Australia and India conference.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;new-deadline-to-submit-your-proposal-is-31st-aug&quot;&gt;
&lt;h2&gt;New deadline to submit your proposal is 31st Aug&lt;/h2&gt;
&lt;p&gt;We added two extra weeks to the deadline because there are enough things to worry about this year, and we wanted to give as many of you the opportunity to prepare your submissions.
Make sure to get your talk in before the new deadline; we already have a lot of great proposals coming in, but we wanted to give everyone a chance to submit their ideas.&lt;/p&gt;
&lt;p&gt;Check out the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/australia/2021/cfp/&quot;&gt;Call for Proposals&lt;/a&gt; page for tips and examples to help inspire you.
And if you’ve got an idea but aren’t sure what to do with it, feel free to ask for feedback on &lt;a class=&quot;reference external&quot; href=&quot;http://slack.writethedocs.org/&quot;&gt;Slack&lt;/a&gt;. Your fellow documentarians will be happy to help!&lt;/p&gt;
&lt;p&gt;We will send out the decision emails to all who submitted by &lt;strong&gt;mid-September&lt;/strong&gt;, and the final talks will be published by &lt;strong&gt;early October&lt;/strong&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;we-ll-have-more-to-share-soon&quot;&gt;
&lt;h2&gt;We’ll have more to share soon&lt;/h2&gt;
&lt;p&gt;We are working through all the other aspects of the event. Expect to hear more about the welcome reception, social event, and more in the next few months.
This will be our fifth Australian conference, and second one for the Indian community, and we can’t wait!&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://www.writethedocs.org/blog/archive/author/write-the-docs-team/atom.xml">
    <title type="text">Announcing speakers</title>
    <id>https://www.writethedocs.org/conf/prague/2021/news/announcing-speakers/</id>
    <updated>2021-07-30T00:00:00Z</updated>
    <published>2021-07-30T00:00:00Z</published>
    <link href="https://www.writethedocs.org/conf/prague/2021/news/announcing-speakers/" />
    <author>
      <name>Write the Docs Team</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;announcing-speakers&quot;&gt;

&lt;p&gt;Hello, documentarians! Today we’re happy to announce the full list of talks and speakers for the 2021 Prague virtual conference.&lt;/p&gt;
&lt;p&gt;Every year talk selection gets more and more difficult as we get a larger, stronger batch of submissions.
Thank you so much to everyone who took the time to send us a pitch –&amp;nbsp;we literally wouldn’t have an event without you!&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;full-speaker-line-up&quot;&gt;
&lt;h2&gt;Full speaker line-up&lt;/h2&gt;
&lt;p&gt;Every year, we look to bring a wide range of voices to the Write the Docs stage. Because being a documentarian can mean different things to different people, we aim for a line-up that spans a good mix of practical, philosophical, and technical topics – with the odd whimsical one thrown in for good measure.&lt;/p&gt;
&lt;p&gt;We’re really excited about the presentations we’ve got this year –&amp;nbsp;we hope you are too!&lt;/p&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-lana-brindley-she-her&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Lana Brindley (she/her)  – More than words: Reviewing and updating your information architecture&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-karen-sawrey&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Karen Sawrey  – Hustling for Fun and Profit as a Technical Writer: A Freelancing Starter Kit&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-fabrizio-ferri-benedetti&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Fabrizio Ferri-Benedetti  – When documenting is designing: How to assist API design as a technical writer&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-jenn-leaver&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Jenn Leaver  – Docs leadership: How to become a stronger leader for your team&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-anita-diamond&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Anita Diamond  – Cognitive Ergonomics in Technical Writing - Lessons from the Field&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-lukas-reu-ner&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Lukas Reußner  – Hitchhiker’s Guide to Documentation Tools and Processes&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-felicity-brand&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Felicity Brand  – How to write a book for (and with) an open source community&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-anna-korinna-n-meth-szab&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Anna Korinna Németh-Szabó  – Alchemy in Adversity (How to become better and more resilient tech writers in a turbulent work environment)&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-victor-sluiter&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Victor Sluiter  – Adventures in setting up a knowledge system for a research group&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-kate-santo&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Kate Santo  – From travel content to technical content: my journey&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-kevin-hwang&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Kevin Hwang  – Customer Feedback is the Fuel in our Engine&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-ryan-macklin-he-they&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Ryan Macklin (he/they)  – So you need to give bad news to users…&lt;/li&gt;
&lt;/ul&gt;
&lt;span class=&quot;target&quot; id=&quot;speaker-kat-stoica-ostenfeld&quot;&gt;&lt;/span&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Kat Stoica Ostenfeld  – How I use applied linguistics to be a better technical writer&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Head over to the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/speakers/&quot;&gt;Speakers page&lt;/a&gt; to see the full abstracts.
We hope that there’s something there for everyone to enjoy, and also something that will broaden your horizons a bit.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;tickets-are-going-fast&quot;&gt;
&lt;h2&gt;Tickets are going fast!&lt;/h2&gt;
&lt;p&gt;If you don’t have your ticket yet, now’s a great time to snap one up. Conference tickets have sold out for the last several years, and they go faster along with the speaker announcement, so if you’re planning to attend, don’t leave it to the last minute.&lt;/p&gt;
&lt;p&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2021/tickets/&quot;&gt;Buy your tickets here!&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Our Opportunity Grant program is still open until August 15th. If buying a ticket is difficult for you, please don’t hesitate to apply to the grant program.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Meetup organizer discount&lt;/strong&gt;: As a thanks to our meetup organizers, we’re happy to offer you a 50% discount on your tickets. Please email us at &lt;a class=&quot;reference external&quot; href=&quot;mailto:prague&amp;#37;&amp;#52;&amp;#48;writethedocs&amp;#46;org&quot;&gt;prague&lt;span&gt;&amp;#64;&lt;/span&gt;writethedocs&lt;span&gt;&amp;#46;&lt;/span&gt;org&lt;/a&gt;, tell us which meetup you organize, and we will send you registration instructions.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;thanks-to-our-sponsors&quot;&gt;
&lt;h2&gt;Thanks to our sponsors&lt;/h2&gt;
&lt;p&gt;We are so grateful to have our sponsors help in bringing these events to life every year. Thanks sincerely to the following companies for supporting the Write the Docs community:&lt;/p&gt;
&lt;blockquote&gt;
&lt;div&gt;&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.redhat.com/en&quot;&gt;Red Hat&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.people-text.de/en/home-en.html&quot;&gt;people text&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.knowledgeowl.com&quot;&gt;KnowledgeOwl&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://www.jetbrains.com/&quot;&gt;JetBrains&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://opencollective.com/open-web-docs&quot;&gt;Open Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://aiven.io/&quot;&gt;Aiven&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://developer.mozilla.org/en-US/&quot;&gt;MDN Web Docs&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;/blockquote&gt;
&lt;p&gt;Head over to our &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/conf/prague/2020/sponsors/prospectus/&quot;&gt;sponsorship prospectus&lt;/a&gt; for details on how your company can get involved!
We have several types of sponsorship available, including tables at the job fair that we’ll be hosting on Tuesday.&lt;/p&gt;
&lt;p&gt;And that’s the latest on the Prague conference. We hope you’re all getting as excited as we are! Stay tuned for more details.&lt;/p&gt;
&lt;p&gt;The Write the Docs Team&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
</feed>
