<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text">Read the Docs Blog - Posts tagged media</title>
  <id>https://blog.readthedocs.com/archive/tag/media/atom.xml</id>
  <updated>2021-12-20T00:00:00Z</updated>
  <link href="https://blog.readthedocs.com" />
  <link href="https://blog.readthedocs.com/archive/tag/media/atom.xml" rel="self" />
  <generator uri="http://ablog.readthedocs.org" version="0.9.5">ABlog</generator>
  <entry xml:base="https://blog.readthedocs.com/archive/tag/media/atom.xml">
    <title type="text">Sphinx and Markdown around the world in 2021</title>
    <id>https://blog.readthedocs.com/sphinx-markdown-2021/</id>
    <updated>2021-12-20T00:00:00Z</updated>
    <published>2021-12-20T00:00:00Z</published>
    <link href="https://blog.readthedocs.com/sphinx-markdown-2021/" />
    <author>
      <name>Juan Luis Cano Rodríguez</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;sphinx-and-markdown-around-the-world-in-2021&quot;&gt;

&lt;p&gt;Read the Docs has been committed to improving the accessibility
and user experience of Sphinx since the start,
and that includes the markup language in which the documentation is written.
Years ago, after carefully listening to users,
&lt;a class=&quot;reference internal&quot; href=&quot;../../../adding-markdown-support/&quot;&gt;&lt;span class=&quot;doc&quot;&gt;we announced recommonmark&lt;/span&gt;&lt;/a&gt;
to help bridging the immense popularity of Markdown
with the powerful capabilities of Sphinx.
(It is now deprecated in favor of MyST - keep reading to know more.)&lt;/p&gt;
&lt;p&gt;It is no surprise that Markdown is in such demand:
thanks in large part to the huge popularity of GitHub,
&lt;a class=&quot;reference external&quot; href=&quot;https://passo.uno/docs-as-code-tools-open-standards/&quot;&gt;Markdown is nowadays the most widely used markup language in open-source
projects&lt;/a&gt;,
ahead of reStructuredText, the second in the list, by an order of magnitude.&lt;/p&gt;
&lt;p&gt;This year, thanks to the CZI Grant we received last year
and the effort of other communities,
especially &lt;a class=&quot;reference external&quot; href=&quot;https://executablebooks.org&quot;&gt;the Executable Book Project&lt;/a&gt;,
we have devoted lots of resources to help consolidate Markdown
as a compelling markup language for Sphinx.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;writing-markdown-in-sphinx&quot;&gt;
&lt;h2&gt;Writing Markdown in Sphinx&lt;/h2&gt;
&lt;p&gt;To that end, we recognized the potential of MyST as a successor of recommonmark,
and &lt;a class=&quot;reference internal&quot; href=&quot;../../../newsletter-april-2021/&quot;&gt;&lt;span class=&quot;doc&quot;&gt;deprecated the latter in favor of MyST-Parser&lt;/span&gt;&lt;/a&gt;.
To &lt;a class=&quot;reference external&quot; href=&quot;https://www.sphinx-doc.org/en/master/usage/markdown.html&quot; title=&quot;(in Sphinx v5.0.0+)&quot;&gt;&lt;span class=&quot;xref std std-doc&quot;&gt;start writing Markdown in Sphinx&lt;/span&gt;&lt;/a&gt;,
you need to follow three steps:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Install &lt;code class=&quot;docutils literal notranslate&quot;&gt;&lt;span class=&quot;pre&quot;&gt;MyST-Parser&lt;/span&gt;&lt;/code&gt;: &lt;code class=&quot;docutils literal notranslate&quot;&gt;&lt;span class=&quot;pre&quot;&gt;pip&lt;/span&gt; &lt;span class=&quot;pre&quot;&gt;install&lt;/span&gt; &lt;span class=&quot;pre&quot;&gt;myst-parser&lt;/span&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Add &lt;code class=&quot;docutils literal notranslate&quot;&gt;&lt;span class=&quot;pre&quot;&gt;myst_parser&lt;/span&gt;&lt;/code&gt; to the list of Sphinx extensions:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class=&quot;highlight-python notranslate&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class=&quot;n&quot;&gt;extensions&lt;/span&gt; &lt;span class=&quot;o&quot;&gt;=&lt;/span&gt; &lt;span class=&quot;p&quot;&gt;[&lt;/span&gt;
    &lt;span class=&quot;c1&quot;&gt;# ...other extensions&lt;/span&gt;
&lt;span class=&quot;hll&quot;&gt;    &lt;span class=&quot;s2&quot;&gt;&amp;quot;myst_parser&amp;quot;&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;]&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;Start writing content in &lt;code class=&quot;docutils literal notranslate&quot;&gt;&lt;span class=&quot;pre&quot;&gt;*.md&lt;/span&gt;&lt;/code&gt; files!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can find more information in the &lt;a class=&quot;reference external&quot; href=&quot;https://myst-parser.readthedocs.io/en/v0.16.0/index.html&quot; title=&quot;(in MyST Parser v0.16.0)&quot;&gt;&lt;span class=&quot;xref std std-doc&quot;&gt;MyST-Parser documentation&lt;/span&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;talks-and-workshops-at-conferences&quot;&gt;
&lt;h2&gt;Talks and workshops at conferences&lt;/h2&gt;
&lt;p&gt;Luckily the migration to MyST-Parser was trivial for most projects,
but we still wanted to spread the word about
the best practices for creating Sphinx projects on Read the Docs using MyST Markdown.
We set the goal of presenting at every large scientific Python event out there,
and all our proposals were accepted &lt;a class=&quot;footnote-reference&quot; href=&quot;#id2&quot; id=&quot;id1&quot;&gt;[1]&lt;/a&gt;! Throughout 2021, we were present in several events:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;We conducted a networking session and a sprint about documentation
at &lt;a class=&quot;reference external&quot; href=&quot;https://www.scipy2021.scipy.org&quot;&gt;SciPy US&lt;/a&gt;,
and in that event we were kindly invited to
the &lt;a class=&quot;reference external&quot; href=&quot;https://www.eventbrite.com/e/sktime-doc-sprint-tickets-164990684579&quot;&gt;sktime documentation sprint&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;We delivered a 90 minutes tutorial called
&lt;a class=&quot;reference external&quot; href=&quot;https://pydata.org/global2021/schedule/presentation/17/document-your-scientific-project-with-markdown-sphinx-and-read-the-docs/&quot;&gt;“Document your scientific project with Markdown, Sphinx, and Read the
Docs”&lt;/a&gt;
at PyData Global,
and we repeated a 120 minute version in Spanish language
at the &lt;a class=&quot;reference external&quot; href=&quot;https://conf.scipy.lat/en/&quot;&gt;SciPy Latin America&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;And we also gave shorter talks at more broadly focused events:
&lt;a class=&quot;reference external&quot; href=&quot;https://www.pylatam.org/&quot;&gt;PyCon Latam&lt;/a&gt; and &lt;a class=&quot;reference external&quot; href=&quot;https://2021.es.pycon.org/&quot;&gt;PyCon Spain&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We have generated workshop material that everybody is welcome to use:&lt;/p&gt;
&lt;ul class=&quot;simple&quot;&gt;
&lt;li&gt;A &lt;a class=&quot;reference external&quot; href=&quot;https://github.com/readthedocs/tutorial-sphinx-markdown&quot;&gt;main repository&lt;/a&gt;
containing some introductory slides about Sphinx,
and detailed notes of every step of the tutorial.&lt;/li&gt;
&lt;li&gt;A &lt;a class=&quot;reference external&quot; href=&quot;https://github.com/readthedocs/tutorial-sphinx-markdown-library/&quot;&gt;supporting repository&lt;/a&gt;
with a tiny Python library that gets used during the tutorial,
inspired by the one used in the &lt;a class=&quot;reference external&quot; href=&quot;https://www.sphinx-doc.org/en/master/tutorial/index.html&quot; title=&quot;(in Sphinx v5.0.0+)&quot;&gt;&lt;span class=&quot;xref std std-doc&quot;&gt;official Sphinx tutorial&lt;/span&gt;&lt;/a&gt;
we authored with the help of the Sphinx community.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And finally, we have also developed an interactive web application to
&lt;a class=&quot;reference external&quot; href=&quot;https://mystyc.herokuapp.com/&quot;&gt;translate small bits of reStructuredText to MyST Markdown&lt;/a&gt;.&lt;/p&gt;
&lt;table class=&quot;docutils footnote&quot; frame=&quot;void&quot; id=&quot;id2&quot; rules=&quot;none&quot;&gt;
&lt;colgroup&gt;&lt;col class=&quot;label&quot; /&gt;&lt;col /&gt;&lt;/colgroup&gt;
&lt;tbody valign=&quot;top&quot;&gt;
&lt;tr&gt;&lt;td class=&quot;label&quot;&gt;&lt;a class=&quot;fn-backref&quot; href=&quot;#id1&quot;&gt;[1]&lt;/a&gt;&lt;/td&gt;&lt;td&gt;We also have submitted a proposal for SciPy India,
which was postponed to January 2022.
EuroSciPy and SciPy Japan didn’t happen in 2021.&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;future-plans&quot;&gt;
&lt;h2&gt;Future plans&lt;/h2&gt;
&lt;p&gt;We are excited to see that the Executable Books team
has released &lt;a class=&quot;reference external&quot; href=&quot;https://pypi.org/project/myst-docutils/&quot;&gt;myst-docutils&lt;/a&gt;,
which should help docutils parse CommonMark directly
and possibly pave the way for Sphinx to parse Markdown
without the need of third party extensions.
Hopefully that will also make it easier for Sphinx
to showcase Markdown content in its documentation more prominently,
and users will be able to naturally pick the markup language
that best suits their needs, be it reST or MyST.&lt;/p&gt;
&lt;p&gt;—&lt;/p&gt;
&lt;p&gt;Considering using Read the Docs for your next Sphinx, Jupyter Book, or MkDocs project?
Check out &lt;a class=&quot;reference external&quot; href=&quot;https://docs.readthedocs.io/&quot;&gt;our documentation&lt;/a&gt; to get started!&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry xml:base="https://blog.readthedocs.com/archive/tag/media/atom.xml">
    <title type="text">Early 2021 talks and podcasts from Read the Docs</title>
    <id>https://blog.readthedocs.com/behind-the-scenes-2021-1/</id>
    <updated>2021-07-06T00:00:00Z</updated>
    <published>2021-07-06T00:00:00Z</published>
    <link href="https://blog.readthedocs.com/behind-the-scenes-2021-1/" />
    <author>
      <name>Juan Luis Cano Rodríguez</name>
    </author>
    <content type="html">&lt;div class=&quot;section&quot; id=&quot;early-2021-talks-and-podcasts-from-read-the-docs&quot;&gt;

&lt;p&gt;During the first half of 2021 several team members of Read the Docs
have talked about the company in podcasts and online events.
If you want to learn more about our company
directly from the people that are a core part of it,
and hear our thoughts on other topics
like open source sustainability and developer advocacy,
this blog post is for you.&lt;/p&gt;
&lt;div class=&quot;section&quot; id=&quot;eric-sustain-podcast&quot;&gt;
&lt;h2&gt;Eric &amp;#64; Sustain podcast&lt;/h2&gt;
&lt;p&gt;&lt;a class=&quot;reference external&quot; href=&quot;https://github.com/ericholscher&quot;&gt;Eric&lt;/a&gt; was the special guest of &lt;a class=&quot;reference external&quot; href=&quot;https://podcast.sustainoss.org/&quot;&gt;Sustain&lt;/a&gt; back in February,
“a podcast about sustaining open source in the long haul”.
Eric started by telling the story of how he and &lt;a class=&quot;reference external&quot; href=&quot;https://github.com/agjohnson&quot;&gt;Anthony&lt;/a&gt; co-founded Read the Docs,
talked about the &lt;a class=&quot;reference external&quot; href=&quot;https://www.writethedocs.org/&quot;&gt;Write the Docs&lt;/a&gt; community,
described the challenges of launching &lt;a class=&quot;reference external&quot; href=&quot;https://www.ethicalads.io/&quot;&gt;EthicalAds&lt;/a&gt; in 2020,
and discussed the opportunities of using ethical advertising to fund open source projects.&lt;/p&gt;
&lt;p&gt;Listen to Eric online:&lt;/p&gt;
&lt;a class=&quot;reference external image-reference&quot; href=&quot;https://podcast.sustainoss.org/66&quot;&gt;&lt;img alt=&quot;../../../_images/eric-sustain.png&quot; class=&quot;align-center&quot; src=&quot;../../../_images/eric-sustain.png&quot; /&gt;&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;juan-luis-data-for-future-podcast&quot;&gt;
&lt;h2&gt;Juan Luis &amp;#64; Data for Future podcast&lt;/h2&gt;
&lt;p&gt;Also in June, &lt;a class=&quot;reference external&quot; href=&quot;https://github.com/astrojuanlu&quot;&gt;Juan Luis&lt;/a&gt; was invited for the second time
to &lt;a class=&quot;reference external&quot; href=&quot;https://dataforfuture.org/&quot;&gt;Data for Future&lt;/a&gt;,
a podcast that seeks to “inspire positive actions
towards an environmentally sustainable and socially just future through technology”.
In an informal conversation,
Juan Luis shared some numbers about the state of software documentation according to several surveys,
promoted the &lt;a class=&quot;reference external&quot; href=&quot;https://diataxis.fr/&quot;&gt;Diátaxis&lt;/a&gt; documentation framework created by Daniele Procida,
discussed his role as Developer Advocate at Read the Docs,
and shared some possible opportunities for collaboration
between Data Science practitioners and technical writers.&lt;/p&gt;
&lt;p&gt;Listen to Juan Luis online:&lt;/p&gt;
&lt;a class=&quot;reference external image-reference&quot; href=&quot;https://dataforfuture.org/episodes/39-making-documentation-sexy-juan-luis-cano-read-the-docs/&quot;&gt;&lt;img alt=&quot;../../../_images/juan-luis-data-for-future.png&quot; class=&quot;align-center&quot; src=&quot;../../../_images/juan-luis-data-for-future.png&quot; /&gt;&lt;/a&gt;
&lt;/div&gt;
&lt;div class=&quot;section&quot; id=&quot;eric-upstream-2021-online-conference&quot;&gt;
&lt;h2&gt;Eric &amp;#64; Upstream 2021 online conference&lt;/h2&gt;
&lt;p&gt;Read the Docs and EthicalAds supported &lt;a class=&quot;reference external&quot; href=&quot;https://upstream.live/&quot;&gt;Upstream 2021&lt;/a&gt; in June,
a one-day online event about “open source, the developers who use it, and the maintainers who make it”.
&lt;a class=&quot;reference external&quot; href=&quot;https://github.com/ericholscher&quot;&gt;Eric&lt;/a&gt; delivered a talk titled &lt;a class=&quot;reference external&quot; href=&quot;https://explore.tidelift.com/upstream/main/session-eric-holscher&quot;&gt;“Bootstrapping a sustainable open source project: The Read the Docs story”&lt;/a&gt;,
in which he dived into some of the less known details of how Read the Docs was created,
shared the different funding strategies the company attempted over the years,
opened up about the dangers of burnout,
and detailed the different commercial plans of Read the Docs
as well as some thoughts about pricing schemes.&lt;/p&gt;
&lt;p&gt;Watch Eric online:&lt;/p&gt;
&lt;a class=&quot;reference external image-reference&quot; href=&quot;https://explore.tidelift.com/upstream/main/session-eric-holscher&quot;&gt;&lt;img alt=&quot;../../../_images/eric-upstream.png&quot; class=&quot;align-center&quot; src=&quot;../../../_images/eric-upstream.png&quot; /&gt;&lt;/a&gt;
&lt;hr class=&quot;docutils&quot; /&gt;
&lt;p&gt;Considering using Read the Docs for your next Sphinx or MkDocs project?
Check out &lt;a class=&quot;reference external&quot; href=&quot;https://docs.readthedocs.io/&quot;&gt;our documentation&lt;/a&gt; to get started!&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>
  </entry>
</feed>
