How We Integrated Our Docs and SDKs As First-Class Citizens of Our Coding Process

Building a great open-source project is not only about writing great code and uploading it to GitHub

Photo by Headway on Unsplash

When we first started building the open-source back-end server, Appwrite, our goal was to make developer’s lives easier.

A lot of the tasks in different projects and even companies are complex, repetitive, and can easily be abstracted, and that’s exactly what Appwrite is trying to do.

Appwrite provides developers with a set of REST APIs and tools that help abstract the complexity and help developers build apps much faster and a lot safer.

But building a great open-source project is not only about writing great code and pushing it to GitHub. It’s about building a great community, having verbose and up-to-date documentation, and allowing easy integration into our API with different tools and technologies.

For Appwrite to be able to make an impact on developers, we wanted to make sure that we treated both our documentation and our SDKs as first-class citizens and not as something we have to figure out at a later stage of the development lifecycle.