It has been said that documentation is like a love letter to your future self. If that's true, then Framer Docs are love letters to our millions of users who rely on them every day for guidance and support. Whether it's a student looking to create a design prototype or a seasoned professional developing a complex interface, Framer Docs cater to everyone in their own language (and code, too).

At Framer, we are dedicated to helping individuals and teams achieve their maximum potential. As such, let's take a closer look at why and how our Docs team uses Framer Projects to manage their 2,396 open-source Docs articles (or 18,545 articles when counting all languages and versions) - which receive over 900,000 daily pageviews from more than 350,000 daily users.

Managing complexity with Framer Projects

Our Docs team comprises 42 fully remote members who are located across the world, including North America, Australia, Europe, and Africa. For such a diverse team working on such a massive project, having a robust project management tool is crucial. Fortunately, Framer Projects meets all our needs. We use it to keep track of our bi-weekly work cycles, prioritize and plan work, make our work visible to the organization, triage issues, and manage releases.

Winning workflows

As you can imagine, Docs articles require a lot of versioning. Some articles are available in all versions, while others are exclusive to Framer.com or Framer Enterprise. Additionally, different articles have various internal conditionals, where a single paragraph or even a word may be relevant in some versions but not in others. This presents a challenge to our team when it comes to managing content.

However, Framer Projects makes it easy by enabling different types of workflows. These workflows (we use both Framer Actions workflows and built-in workflows) allow us to capture everything accurately, which is especially important for launches. For example, for each launch, we may need to create more than 50 new articles, while a regular day may involve 15 to 20 pull requests and several updates. Different workflows keep everything organized and on track.