Download websites that use Retype

About Retype

Documentation sites have an unusual property: they are generated once and then left alone until the next release. Retype belongs to the family of tools that turn a folder of Markdown into a browsable site with search, navigation and a theme, and the output is static, so what our crawler sees is markup the generator produced on the day somebody last ran the build.

The consequence is that the version field means something here that it does not mean for a running application. A server can be patched underneath a live site without anyone touching the content. A generated site cannot, because its version is frozen at build time and stays frozen until someone regenerates it. As of October 2026 we record Retype on 58 sites across 11 distinct versions, with 4.6.0 appearing more often than any other in our data. Reading that distribution as a staleness map is fair. A site sitting on an old generator release is a site whose documentation has not been rebuilt in a long while, which usually means the product it documents has not shipped in a long while either.

Presence also says something about how a team works. Choosing a generator over a hosted documentation platform is a decision to keep documentation in the repository, inside code review and under the same version control as the software, and to spend engineering time rather than a subscription line. Licensing is Freemium, so a free tier covers small projects and payment appears only when a team needs more, which means the count mixes hobby repositories, internal handbooks and commercial products documenting a paid API. Our Static site generator label is a rough fit at best, since nothing is being managed at request time.

Detection rests on generated markup and asset paths, and a static site is easy to strip. Teams that publish under their own domain, put a content delivery network in front, or customize the theme heavily can remove the marks that identify the generator, and there is no runtime left to announce itself. Undercounting is the expected direction of error. The version we report is also the version stamped into the build, not necessarily the release installed on the machine that produced it, so treat it as a build record rather than an inventory of what the team runs today.

The audience for a list like this is narrow and knows what it wants. Vendors of documentation platforms use it to find teams already committed to documentation as code, which is a shorter conversation than selling the idea itself. Developer tool companies use it to find products with a public API surface worth integrating against. Anyone studying this tooling market needs the population, because Object.NET publishes no customer list and a generated site phones nobody home. A lookup confirms one site. Only the export shows how large the group is, how old its builds are, and where it overlaps with the competing generators.