How Foursquare Succeeded In Managing Developers’ Documentation
Tags: api, documentation, foursquare
Published: 2019-02-19 11:02:05

---
title: How Foursquare Succeeded In Managing Developers’ Documentation
published: true
description: 
tags: APIs, documentation, Foursquare
---

One of the most important but often overlooked aspects of building a strong developers’ community is DOCUMENTATION. Therefore it is always a good practice to see how the big players are already handling such issues.

In this article, I will give you a short overview of how [Foursquare](https://foursquare.com/) has managed to successfully deal with this stuff.

After reviewing the existing documentation they’ve launched an entirely new version of [developer.foursquare.com](https://developer.foursquare.com/), full of features *“to help developers get started and explore their location intelligence tools"*.



There are two areas I want to cover in this short overview: Infrastructure and Feature Improvements.

#INFRASTRUCTURE IMPROVEMENTS
**✔ Content management **— [Jekyll](https://jekyllrb.com/) **framework** is used to convert markdown documents into a reusable documentation platform while **custom plugins** help with faster and easier documentation update

**✔ Deployment **—  there is a **script** used for building an image from Dockerfile and exposing Foursquare’s pages via [Nginx](https://nginx.org/en/) web server

**✔ Automation **—  to decouple docs and allow fast live updates, **buildings** are **picked up automatically** via [Travis-Ci](http://travis-ci.com/)

#FEATURE IMPROVEMENTS
**✔ Searching** —  with the use of [ElasticSearch] (https://www.elastic.co/) Foursquare built a search engine reindexing with every docs site update. The search engine enables devs to find specific keywords, endpoints or error responses. What’s even more, the company has created an API allowing seamless integration to 3rd parties. Hence, integrating directly into IDEs like Android Studio and Xcode is easy

**✔ Endpoint Pages**—  due to the fact that endpoint pages have API responses, which is absolutely great, developers can easily see the expected output from endpoints

**✔ Sample Apps & Libraries**  — there have appeared additional [Sample Apps](https://developer.foursquare.com/docs/sample-apps). Thanks to them you can, for example, find the nearest coffee shop, pick a spot to jump out for a ride or even explore the real world through Augmented Reality. As for the new [Client Libraries](https://developer.foursquare.com/docs/api/libraries), they are now featured with support for Swift and Go

— — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Well, If you haven’t used Foursquare’s API yet, feel free to study their **[getting started guide](https://developer.foursquare.com/docs/api/getting-started)**. You will be able to create an account and have your first API call in 5 easy steps.

Based on: [A New Experience for Developer Documentation & Resources](https://medium.com/foursquare-direct/a-new-experience-for-developer-documentation-resources-f753ee1ba51?fbclid=IwAR3uKULZ9NpzxJPCMp9vW_evyDTjatdMnV-ZaywearnzJ_b982kq8hEjYAU) by Arin Ray.

[Original post](https://javashop.pl/how-foursquare-succeeded-in-managing-developers-documentation/).