---
title: "Develop"
description: "Build upon, extend, or integrate with the product to create additional value."
doc_version: "2025-01-09"
last_updated: "2026-08-08"
canonical_url: "https://7act.org/actions/develop/"
language: "en"
license: "CC BY 4.0"
---

# Develop

Users often need to build upon, extend, or integrate with existing products. This isn't just about coding - it's about creating additional value on top of the core product, whether through integrations, extensions, plugins, or entirely new applications.

Examples of docs that address developing products further are [Vercel's Approval Checklist](https://vercel.com/docs/integrations/create-integration/approval-checklist) and [Chrome's Debug extensions](https://developer.chrome.com/docs/extensions/get-started/tutorial/debug). Notice that the focus is almost always pragmatic, the content type largely irrelevant. Many integration or extension docs take the form of guides or even articles.

Documentation that focuses on development or integration needs acts as a bridge between the product's current capabilities and its potential. It transforms users into co-creators, fostering an ecosystem. This documentation type often becomes the foundation for communities of practice.


## What the user wants to do

Users often need to build upon, extend, or integrate with existing products — through integrations, extensions, plugins, or entirely new applications. The focus is almost always pragmatic.

## Signals that your docs miss it

- Integration and extension questions go unanswered or to a forum.
- There is no guide for building on top of the product.
- The product's extension points are undocumented.

## Two examples in the wild

- [Vercel Approval Checklist](https://vercel.com/docs/integrations/create-integration/approval-checklist)
- [Chrome Debug extensions](https://developer.chrome.com/docs/extensions/get-started/tutorial/debug)

## Common content types

- DITA: <task>, <codeblock>, <coderef>
- Diataxis: How-to guide
- Good Docs Project: How-to guide, API reference

## One metric

ecosystem growth — Number of integrations or extensions built by users.

## Sitemap

- [Seven-Action Documentation Model](https://7act.org/index.md)
- [Introduction](https://7act.org/rationale/index.md)
- [Actions](https://7act.org/actions/index.md)
- [Appraise](https://7act.org/actions/appraise/index.md)
- [Understand](https://7act.org/actions/understand/index.md)
- [Explore](https://7act.org/actions/explore/index.md)
- [Practice](https://7act.org/actions/practice/index.md)
- [Remember](https://7act.org/actions/remember/index.md)
- [Develop](https://7act.org/actions/develop/index.md)
- [Troubleshoot](https://7act.org/actions/troubleshoot/index.md)
- [Glossary](https://7act.org/glossary/index.md)
- [Seven-Action Documentation skill](https://7act.org/skill/index.md)