DevDocs — API Documentation Browser
DevDocs combines multiple developer documentations in a clean and organized web UI with instant search, offline support, mobile version, dark theme, keyboard shortcuts, and more.
DevDocs was created by Thibaut Courouble and is operated by freeCodeCamp.
Please reach out to the community on Discord if you would like to join the team!
Keep track of development news:
Table of Contents: Quick Start · Vision · App · Scraper · Commands · Contributing · Documentation · Related Projects · License · Questions?
Unless you wish to contribute to the project, we recommend using the hosted version at devdocs.io. It's up-to-date and works offline out-of-the-box.
The easiest way to run DevDocs locally is using Docker:
docker run --name devdocs -d -p 9292:9292 ghcr.io/freecodecamp/devdocs:latestThis will start DevDocs at localhost:9292. We provide both regular and Alpine-based images:
ghcr.io/freecodecamp/devdocs:latest- Standard imageghcr.io/freecodecamp/devdocs:latest-alpine- Alpine-based (smaller size)
Images are automatically built and updated monthly with the latest documentation.
Alternatively, you can build the image yourself:
git clone https://github.com/freeCodeCamp/devdocs.git && cd devdocs
docker build -t devdocs .
docker run --name devdocs -d -p 9292:9292 devdocsDevDocs is made of two pieces: a Ruby scraper that generates the documentation and metadata, and a JavaScript app powered by a small Sinatra app.
DevDocs requires Ruby 4.0.6 (defined in Gemfile), libcurl, bsdtar (included in macOS, the libarchive-tools package on Debian and Alpine), and a JavaScript runtime supported by ExecJS (included in OS X and Windows; Node.js on Linux). On Arch Linux run pacman -S ruby ruby-bundler ruby-erb ruby-irb.
Once you have these installed, run the following commands:
git clone https://github.com/freeCodeCamp/devdocs.git && cd devdocs
gem install bundler
bundle install
bundle exec thor docs:download --default
bundle exec rackupFinally, point your browser at localhost:9292 (the first request will take a few seconds to compile the assets). You're all set.
The thor docs:download command is used to download pre-generated documentations from DevDocs's servers (e.g. thor docs:download html css). You can see the list of available documentations and versions by running thor docs:list. To update all downloaded documentations, run thor docs:download --installed. To download and install all documentation this project has available, run thor docs:download --all.
Note: there is currently no update mechanism other than git pull origin main to update the code and thor docs:download --installed to download the latest version of the docs. To stay informed about new releases, be sure to watch this repository.
DevDocs aims to make reading and searching reference documentation fast, easy and enjoyable.
The app's main goals are to:
- Keep load times as short as possible
- Improve the quality, speed, and order of search results
- Maximize the use of caching and other performance optimizations
- Maintain a clean and readable user interface
- Be fully functional offline
- Support full keyboard navigation
- Reduce “context switch” by using a consistent typography and design across all documentations
- Reduce clutter by focusing on a specific category of content (API/reference) and indexing only the minimum useful to most developers.
Note: DevDocs is neither a programming guide nor a search engine. All our content is pulled from third-party sources and the project doesn't intend to compete with full-text search engines. Its backbone is metadata; each piece of content is identified by a unique, "obvious" and short string. Tutorials, guides and other content that don't meet this requirement are outside the scope of the project.
The web app is all client-side JavaScript, powered by a small Sinatra/Sprockets application. It relies on files generated by the scraper.
Many of the code's design decisions were driven by the fact that the app uses XHR to load content directly into the main frame. This includes stripping the original documents of most of their HTML markup (e.g. scripts and stylesheets) to avoid polluting the main frame, and prefixing all CSS class names with an underscore to prevent conflicts.
Another driving factor is performance and the fact that everything happens in the browser. A service worker (which comes with its own set of constraints) and localStorage are used to speed up the boot time, while memory consumption is kept in check by allowing the user to pick his/her own set of documentations. The search algorithm is kept simple because it needs to be fast even searching through 100,000 strings.
DevDocs being a developer tool, the browser requirements are high:
- Recent versions of Firefox, Chrome, or Opera
- Safari 16.4+
- Edge 89+
- iOS 16.4+
The app is served as ES modules resolved through an import map, which is the newest thing it relies on and what sets the versions above. This allows the code to take advantage of the latest DOM and HTML5 APIs and make developing DevDocs a lot more fun!
The scraper is responsible for generating the documentation and index files (metadata) used by the app. It's written in Ruby under the Docs module.
There are currently two kinds of scrapers: UrlScraper which downloads files via HTTP and FileScraper which reads them from the local filesystem. They both make copies of HTML documents, recursively following links that match a set of rules and applying all sorts of modifications along the way, in addition to building an index of the files and their metadata. Documents are parsed using Nokogiri.
Modifications made to each document include:
- removing content such as the document structure (
<html>,<head>, etc.), comments, empty nodes, etc. - fixing links (e.g. to remove duplicates)
- replacing all external (not scraped) URLs with their fully qualified counterpart
- replacing all internal (scraped) URLs with their unqualified and relative counterpart
- adding content, such as a title and link to the original document
- ensuring correct syntax highlighting using Prism
These modifications are applied via a set of filters using the HTML::Pipeline library. Each scraper includes filters specific to itself, one of which is tasked with figuring out the pages' metadata.
The end result is a set of normalized HTML partials and two JSON files (index + offline data). Because the index files are loaded separately by the app following the user's preferences, the scraper also creates a JSON manifest file containing information about the documentations currently available on the system (such as their name, version, update date, etc.).
More information about scrapers and filters is available in the docs folder.
The command-line interface uses Thor. To see all commands and options, run thor list from the project's root.
# Server
rackup # Start the server (ctrl+c to stop)
rackup --help # List server options
# Docs
thor docs:list # List available documentations
thor docs:download # Download one or more documentations
thor docs:manifest # Create the manifest file used by the app
thor docs:generate # Generate/scrape a documentation
thor docs:page # Generate/scrape a documentation page
thor docs:package # Package a documentation for use with docs:download
thor docs:clean # Delete documentation packages and cached responses
# Console
thor console # Start a REPL
thor console:docs # Start a REPL in the "Docs" module
# Tests can be run quickly from within the console using the "test" command.
# Run "help test" for usage instructions.
thor test:all # Run all tests
thor test:docs # Run "Docs" tests
thor test:app # Run "App" tests
thor test:coverage # Run coverage report on "App" tests
# Assets
thor assets:compile # Compile assets (not required in development mode)
thor assets:clean # Clean old assetsIf multiple versions of Ruby are installed on your system, commands must be run through bundle exec.
Contributions are welcome. Please read the contributing guidelines.
Below are some helpful shortcuts and usage tips that are not immediately obvious to new users:
- Press / or Ctrl + K to instantly focus the search bar.
- Press ? to open DevDocs’ built-in help overlay.
- Press ↑ or ↓ to navigate search results without touching the mouse.
- Press Enter to open the highlighted search result.
- Press Backspace to go back to the previously viewed page.
- Press Shift + S to toggle the sidebar visibility.
- Press A to open the list of all installed documentation sets.
- Press Esc to close popups, overlays, and search.
- Use the ⚡ Offline Mode toggle to download docs for offline use.
- You can pin specific documentation sets to the sidebar for quicker access.
These shortcuts make DevDocs faster to navigate and more efficient for daily use.
Made something cool? Feel free to open a PR to add a new row to this table! You might want to discover new projects via https://github.com/topics/devdocs.
| Project | Description | Last commit | Stars |
|---|---|---|---|
| yannickglt/alfred-devdocs | Alfred workflow | ||
| Merith-TK/devdocs_webapp_kotlin | Android application | ||
| gruehle/dev-docs-viewer | Brackets extension | ||
| egoist/devdocs-desktop | Electron application | ||
| skeeto/devdocs-lookup | Emacs function | ||
| astoff/devdocs.el | Emacs viewer | ||
| naquad/devdocs-shell | GTK shell with Vim integration | ||
| hardpixel/devdocs-desktop | GTK application | ||
| qwfy/doc-browser | Linux application | ||
| dteoh/devdocs-macos | macOS application | ||
| Sublime Text plugin | Sublime Text plugin | ||
| mohamed3nan/DevDocs-Tab | VS Code extension (view as tab) | ||
| deibit/vscode-devdocs | VS Code extension (open the browser) | ||
| mdh34/quickDocs | Vala/Python based viewer | ||
| girishji/devdocs.vim | Vim plugin & TUI (browse inside Vim) | ||
| romainl/vim-devdocs | Vim plugin | ||
| waiting-for-dev/vim-www | Vim plugin | ||
| emmanueltouzery/apidocs.nvim | Neovim plugin | ||
| toiletbril/dedoc | Terminal based viewer | ||
| Raycast Devdocs | Raycast extension | Unavailable | Unavailable |
| chrisgrieser/alfred-docs-searches | Alfred workflow |
Copyright 2013–2026 Thibaut Courouble and other contributors
This software is licensed under the terms of the Mozilla Public License v2.0. See the COPYRIGHT and LICENSE files.
Please do not use the name DevDocs to endorse or promote products derived from this software without the maintainers' permission, except as may be necessary to comply with the notice/attribution requirements.
We also wish that any documentation file generated using this software be attributed to DevDocs. Let's be fair to all contributors by giving credit where credit's due. Thanks!
If you have any questions, please feel free to ask them on the #contributors chat room on Discord.