# Use the practical toolkit

Templates, checklists, and examples you can copy directly into your own project. Each item is clearly labeled as either a **template** (a starting point you adapt) or a **worked example** (a finished illustration you study).

## Foundation

  - [**Information types**](https://docs.redaction-technique.org/en/toolkit/information-types/): The architectural foundation: Concepts, Tasks, and References, their relationship to DITA, and how they shape our authoring templates.

## Templates

  - [**Concept article template**](https://docs.redaction-technique.org/en/toolkit/concept-article-template/): Definition, why it matters, key principles, examples, trade-offs.
  - [**Task article template**](https://docs.redaction-technique.org/en/toolkit/task-article-template/): Objective, prerequisites, steps, expected result, troubleshooting.
  - [**Reference article template**](https://docs.redaction-technique.org/en/toolkit/reference-article-template/): Overview, syntax, parameters, examples, limitations.
  - [**API documentation template**](https://docs.redaction-technique.org/en/toolkit/api-documentation-template/): One endpoint per page: method, parameters, request/response, error codes.
  - [**Documentation project plan**](https://docs.redaction-technique.org/en/toolkit/documentation-project-plan-template/): Goal, audience, scope, format, success criteria, timeline.
  - [**Documentation review request**](https://docs.redaction-technique.org/en/toolkit/documentation-review-request-template/): Scope a review so it actually gets done.

## Checklists

  - [**Documentation quality**](https://docs.redaction-technique.org/en/toolkit/documentation-quality-checklist/): Run before merging any documentation change.
  - [**Technical review**](https://docs.redaction-technique.org/en/toolkit/technical-review-checklist/): What a subject-matter-expert reviewer should and shouldn
  - [**Release readiness**](https://docs.redaction-technique.org/en/toolkit/release-readiness-checklist/): A gate for shipping docs alongside a product release.
  - [**Documentation migration**](https://docs.redaction-technique.org/en/toolkit/documentation-migration-checklist/): Moving between formats or platforms without losing content or URLs.
  - [**Docs-as-code adoption**](https://docs.redaction-technique.org/en/toolkit/docs-as-code-adoption-checklist/): Format, version control, CI/CD, and team readiness.
  - [**Documentation audit**](https://docs.redaction-technique.org/en/toolkit/documentation-audit-checklist/): Find orphaned pages, duplicates, and stale content.

## Examples

  - [**A well-structured Markdown page**](https://docs.redaction-technique.org/en/toolkit/example-markdown-page/): An annotated concept article, explaining each structural choice.
  - [**A documentation repository structure**](https://docs.redaction-technique.org/en/toolkit/example-repository-structure/): Locale-first content, separated from tooling and assets.
  - [**A basic docs-as-code workflow**](https://docs.redaction-technique.org/en/toolkit/example-docs-as-code-workflow/): One change, branch to production, annotated step by step.
  - [**A documentation review workflow**](https://docs.redaction-technique.org/en/toolkit/example-review-workflow/): Splitting technical review from editorial review, and why.
  - [**A practical CI/CD pipeline**](https://docs.redaction-technique.org/en/toolkit/example-cicd-pipeline/): Build, test, link-check, preview, deploy — annotated stage by stage.

---

Source: https://docs.redaction-technique.org/en/toolkit/