Documentation Engineering on ProBase

Creating a Company Handbook - Scalable, Text-Based, and Future-Proof

Sat, 11 Apr 2026 00:00:00 +0000

Creating a Company Handbook: Scalable, Text-Based, and Future-Proof

A company handbook is more than a collection of documents – it is the central nervous system of an organization. It creates transparency, makes knowledge accessible, and enables teams to collaborate efficiently. But how do you design a handbook that grows with the company, remains technically flexible, and works without proprietary tools?

This article shows how to build a handbook that is scalable, text-based, and version-controlled – from individual knowledge collections to enterprise-wide documentation systems. We rely on open-source formats like Markdown with Mermaid or AsciiDoc with PlantUML, as well as tools that support these approaches.

What you can do with plaintext formats

Sat, 14 Mar 2026 00:00:00 +0000

Introduction to the Plain Text World

Digital content is created today in a wide variety of forms: websites, documentation, presentations, or technical diagrams. Traditionally, such content is often created with graphical tools—such as Word, PowerPoint, or drawing programs. These tools are intuitive but have a crucial disadvantage: the content is usually stored in proprietary file formats and is difficult to automate, version, or process further.

An alternative to this is plain text formats. Here, content is not described visually but via a simple, text-based syntax. These files can be edited with any text editor, easily versioned, and automatically processed further.

Once-Only in Documentation

Sat, 14 Feb 2026 00:00:00 +0000

What is the Once-Only Principle?

The Once-Only principle states: Data or information should be captured, stored, and maintained only once – and reused at all relevant points. It avoids redundancy, minimizes sources of error, and reduces maintenance effort. Originally known from public administration and e-government, it is gaining increasing importance in technical documentation – especially in complex, agile, and scalable systems.

Why is Once-Only Important in Documentation?

In software projects, documentation often grows in an uncoordinated manner:

Several ways to model dataflows

Sat, 17 Jan 2026 00:00:00 +0000

Data Flow or Information Flow?

Data flow describes the transmission of raw, unprocessed data, regardless of its business meaning.

In contrast, information flow concerns the transmission of processed or interpreted data that provides the recipient with clear and recognizable value.

Naturally, in an IT environment, when information needs to be transferred, this occurs based on data transfer. Data flow forms the technical foundation for information flow.

The representation forms described in this article use elements of both variants, but the purpose of the information flow is the primary focus.