Page Views¶

Our stats:

• 400 Million Page Views (up from 338M, 18%)

• 77 Million Unique Visitors (up from 75M, 3%)

These numbers are not completely accurate, since we implemented Do Not Track support in May, our analytics pageview figures understate our actual traffic. We estimate that around 6% of users are not counted here. We also don’t count all the users who block Google Analytics with a browser extension.

Site Stats¶

The stats, in total numbers:

• 100,000 projects (up from 77k, 30%)

• 155,000 users (up from 103k, 50%)

We have been battling spam quite heavily again this year, so these numbers are a bit skewed.

Community¶

This year, we had:

• 28 people who committed code to the main repository (up from 23, 22%)

• 3774 commits (up from 1058, 257%)

• 797 issues - 189 open, 608 closed (up from 513, 55%)

You can see the number of commits and issues has gone up quite a bit. This is largely because of the additional staffing we have had on the project, allowing us to be more active to both our users and to release more features.

Funding¶

• $294,000 in revenue from readthedocs.org (up from $218,000, 35%)

• $278,000 from advertising (up 59%)

• $16,000 from Gold users (up 16%)

• We have additional revenue from our commercial offering at readthedocs.com, but aren’t including that in our community funding overview

The biggest impact to our revenue this year was our ads being blocked. This happened in May, and caused an initial 32% reduction in our ad revenue. We were added to the Acceptable Ads list later in the month, which regained around half of our revenue. So for the second half of the year, our ad revenue was down about 15%.

We are also exploring sharing revenue with our documentation authors. There are currently 3 projects enrolled in a revenue share, and we’re hoping to expand that in 2019 to better support open source projects.

The project is now on firm financial footing. We have a cash reserve that will allow us to pay all of our staff for more than 3 months in the event of a loss of revenue, which allows us to be more flexible with our revenue going forward. This funding allowed us to expand from 4 to 5 full-time folks working on the project.

We also moved hosting to Azure this year in August from Rackspace, who both have sponsored our hosting.

Conclusion¶

This year we’ve continued to invest in our ethical advertising approach, growing our team by one member and building lots of new features. It feels like the project is progressing quite well, and we’re committing way more code and dealing with a much larger number of user issues.

It feels like success to be able to properly support our community by improving the product, while creating a business model that we can be proud of.