Posts from Bend, Oregon
🏝️ A few team members took vacations this month, and everything kept running smoothly, which is always wonderful to see.
⏩ Our git cloning code was refactored, and now projects should be building much faster. The more git branches and tags you have, the faster the build will be.
🚀 We shipped support for customizing the URL path for projects and subprojects, allowing you to remove or customize the /projects/ path on subprojects. This is enabled via Support request currently, and only on certain plans on Read the Docs for Business.
🛣️ Deprecations underway:
We have a number of old feature deprecations underway.
The goal here is to reduce complexity of our build platform,
and enable users to control their own builds via
build.commands instead of feature flags.
Keep an eye on your email for any deprecation notifications that might impact your project.
September was exciting because a few members of our team finally got to gather in person. Manuel, Benjamin, and Eric all attended Djangocon Europe in September, and had lots of great discussions around documentation.
Also, as we mentioned, in Q4 we’re going to be focusing on our core platform features. This means we’ll have fewer new features to talk about, but lots of smaller improvements to the overall experience of using Read the Docs.
Our focus for August has continued to be around marketing and community outreach. We continue to better understand how our customers view our product, and work with them to use it well.
We’re working to establish our goals for Q4 2022, and it looks like continued focus on polishing core platform features. We have a lot of features, and we need to continue making them easier to use.
We continue to be excited about the expanded capacity we have with an additional team member. Our focus for July has been around a lot of marketing and positioning, trying to better understand how our customers view our product, and work with them to use it well.
We also had our 12th birthday just before publishing this newsletter. 🎉
Summer has come, which means our overall development has slowed a bit as the team takes some well-deserved vacation time. That said, we’re still excited about our recent hire and the ongoing work we’ve been doing to support the documentation ecosystem.
Our focus for Q3 (July-Sept) of 2022 is around improving our frontend and marketing pages. This includes a fancy new marketing website, as well as a revamped dashboard UX that will make many features nicer for our users.
We’re excited to welcome Benjamin Balder Bach to our team, joining as a part-time contractor for now. He’s a developer with a history of working as an Open Source maintainer and event organizer in the Django community. He has also previously contributed to Read the Docs and will be a wonderful addition to the team.
We’re also excited to see people using our new build.jobs feature that we previously announced. There are a lot of interesting ways to adapt the build process with this, and we’ll continue to watch with interest how people are using it!
April has been another exciting month here at Read the Docs. We’ve gotten a few good candidates for our Product-focused Application Developer job posting, and we’re on to the second round of interviews. Expect to hear more about any new team members here in the next couple months.
We’ve continued building a number of features and bug fixes in our roadmap:
March has been a productive month for Read the Docs. We have finished our Product-focused Application Developer job posting, which we’re excited about. We plan to share this on a few job boards, and are looking for someone to join the team who is excited to work on our product.
We’ve continued building a number of features and bug fixes in our March roadmap:
It’s been pretty quiet on the company front in February, with nothing much to report. We’re actively working on our latest job description, which will be a product-focused Python development position. If you’re interested, please let us know.
In February we continued to work on refactors and internal changes. Among the major user-facing changes:
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.
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.
- 05 February 2021
- Bend, Oregon
Update: The migration was successful and the site has been fully restored as of 4PM PST.
We wanted to make you aware that on Friday, February 12th at 1pm PST (4pm EST, 21:00 UTC), Read the Docs Community (readthedocs.org) will be having a scheduled dashboard downtime of approximately 4 hours.
- 27 January 2021
- Bend, Oregon
We’re excited to announce that Pull Request building is now available for all Read the Docs users. We have been working on this feature for over a year, and having it available for all our users is a major milestone.
This feature allows users to confirm documentation builds correctly for all of their commits, not just ones merged into branches that are activated on Read the Docs. This moves documentation into your continuous integration pipeline, and improves the workflow for everyone working on documentation.
- 25 January 2021
- Bend, Oregon
Update: This maintenance window has concluded at 5:40 PM PST.
We wanted to make you aware that on Friday, February 5 at 5:00pm PST (8:00pm EST, Saturday 01:00 UTC), Read the Docs for Business (readthedocs.com) will be having a scheduled downtime of approximately 2 hours.
- 06 January 2021
- Bend, Oregon
Read the Docs received a grant to support scientific software at the beginning of this year. As part of this, we are hiring for two new positions related to the grant work: