Read the Docs Blog - Posts by Eric Holscherhttps://blog.readthedocs.com/archive/author/eric-holscher/atom.xml2022-03-10T00:00:00ZABlogRead the Docs newsletter - March 2022https://blog.readthedocs.com/newsletter-march-2022/2022-03-10T00:00:00Z2022-03-10T00:00:00ZEric Holscher<div class="section" id="read-the-docs-newsletter-march-2022">
<p>It’s been pretty quiet on the company front in February,
with nothing much to report.
<strong>We’re actively working on our latest job description,
which will be a product-focused Python development position.</strong>
If you’re interested, please <a class="reference external" href="mailto:hello%40readthedocs.org?subject=Job%20Posting">let us know</a>.</p>
<div class="section" id="new-features">
<h2>New features</h2>
<p>In February we continued to work on refactors and internal changes.
Among the major user-facing changes:</p>
<ul class="simple">
<li><strong>We now have the CDN on Read the Docs for Business in beta</strong>, with a couple accounts testing it. If you’re interested, please <a class="reference external" href="mailto:hello%40readthedocs.org">contact us</a>.</li>
<li>You can now <a class="reference external" href="https://github.com/readthedocs/readthedocs.org/pull/8850">cancel builds</a> via a button in the dashboard. This will save resources, and allow you to ensure that you don’t hit concurrency limits if you trigger a few builds at once.</li>
<li>Projects that are imported via the API are now required to have a VCS repository linked to them, if your organization has <a class="reference external" href="https://docs.readthedocs.io/en/latest/commercial/single-sign-on.html#sso-with-vcs-provider-github-bitbucket-or-gitlab">VCS SSO</a> turned on, so that users will be able to access it.</li>
</ul>
<p>You can always see the latest changes to our platforms in our <a class="reference external" href="https://docs.readthedocs.io/en/stable/changelog.html" title="(in Read the Docs user documentation v7.4.1)"><span class="xref std std-doc">Read the Docs
Changelog</span></a>.</p>
</div>
<div class="section" id="upcoming-features">
<h2>Upcoming features</h2>
<ul class="simple">
<li><strong>We’re working on pre and post-build steps</strong>, and hope to have those released in the next week or two. This is a long-requested feature that we’re really excited to be able to share with folks.</li>
<li>We’re getting much closer on our landing page update. They are being served from a super secret URL, and will be made our official front page before long…</li>
<li>We continue to work on tracking 404 pages in our project analytics,
so that projects can easily fix up missing or outdated page links.</li>
<li>We have <a class="reference external" href="https://github.com/readthedocs/readthedocs.org/issues/8811">made process on support</a> for multiple projects in a single git repo.</li>
</ul>
</div>
<div class="section" id="possible-issues">
<h2>Possible issues</h2>
<ul class="simple">
<li>We are still watching Sphinx upgrades for possible issues they might cause around the ecosystem.</li>
<li>We are also tracking the upcoming <a class="reference internal" href="../../../github-git-protocol-deprecation/"><span class="doc">Deprecation of the git:// protocol on GitHub</span></a> to ensure that it will have minimal impact for our users.</li>
</ul>
<hr class="docutils" />
<p>Considering using Read the Docs for your next Sphinx or MkDocs project?
Check out <a class="reference external" href="https://docs.readthedocs.io/">our documentation</a> to get started!</p>
</div>
</div>
Read the Docs newsletter - February 2022https://blog.readthedocs.com/newsletter-february-2022/2022-02-08T00:00:00Z2022-02-08T00:00:00ZEric Holscher<div class="section" id="read-the-docs-newsletter-february-2022">
<p>Welcome to the latest edition of our monthly newsletter, where we
share the most relevant updates around Read the Docs,
offer a summary of new features we shipped
during the previous month,
and share what we’ll be focusing on in the near future.</p>
<div class="section" id="company-updates">
<h2>Company updates</h2>
<ul class="simple">
<li>We have mostly finished migrating Read the Docs for Business users to Cloudflare for SSL.
There are lots of interesting features this will enable,
so stay tuned for updates there.</li>
<li>We’re sad to announce that <a class="reference external" href="https://github.com/astrojuanlu">Juan Luis</a> has moved on from Read the Docs as our developer advocate.
The work he did was vital towards getting our <a class="reference internal" href="../../../czi-grant-announcement/"><span class="doc">CZI grant</span></a> mostly finished, and we thank him for his time spent bettering the RTD, Sphinx, and docs community.</li>
<li>On a related note, we’re going to be hiring again soon to fill another position.
It will be a bit different and likely a product-focused Python development position.
If you’re interested, please <a class="reference external" href="mailto:hello%40readthedocs.org?subject=Job%20Posting">let us know</a>.</li>
</ul>
</div>
<div class="section" id="new-features">
<h2>New features</h2>
<p>In January we continued to work on refactors and internal changes.
Among the major user-facing changes:</p>
<ul class="simple">
<li>We fixed a bug in Bitbucket that didn’t allow us to properly sync user permissions.
This resulted in a few support requests, but has now been resolved.</li>
<li>We improved our ability to mark projects as non-spam,
so that we can validate a project isn’t spam and then make sure it doesn’t get flagged by our automated system.</li>
</ul>
<p>You can always see the latest changes to our platforms in our <a class="reference external" href="https://docs.readthedocs.io/en/stable/changelog.html" title="(in Read the Docs user documentation v7.4.1)"><span class="xref std std-doc">Read the Docs
Changelog</span></a>.</p>
</div>
<div class="section" id="upcoming-features">
<h2>Upcoming features</h2>
<ul class="simple">
<li>Cancelling a build is a long requested feature, and we’re getting close to implementing it.</li>
<li>We’re looking at tracking 404 pages in our project analytics,
so that projects can easily fix up missing or outdated page links.</li>
<li>We are hoping to launch our revamped landing pages this month,
which will give our front page a much needed refresh.</li>
<li>We are working to define a policy for canonical docs and cloned versions,
so that we can more easily remove outdated docs for projects.</li>
<li>We’re working to investigate supporting a CDN on Read the Docs for Business,
which will be an exciting new feature for our users there.</li>
<li>We’re <a class="reference external" href="https://github.com/readthedocs/readthedocs.org/issues/8811">looking at how to support</a> multiple <code class="docutils literal notranslate"><span class="pre">readthedocs.yml</span></code> files in a single git repo.</li>
</ul>
</div>
<div class="section" id="possible-issues">
<h2>Possible issues</h2>
<p>We continue to see a good pace of development on the Sphinx project,
with them adding support for docutils 0.18,
and removing jQuery in a major refactor of their Javascript.
We’re working to ensure that our theme and other parts of the ecosystem don’t break with these changes,
and trying to be procative to address any possible issues.
That said,
there will likely still be some issues that sneak through with the release of Sphinx 4.5 (docutils upgrade) and Sphinx 5.0 (JS refactor).</p>
<hr class="docutils" />
<p>Considering using Read the Docs for your next Sphinx or MkDocs project?
Check out <a class="reference external" href="https://docs.readthedocs.io/">our documentation</a> to get started!</p>
</div>
</div>