Every Page is Page One

 

    Every Page is Page One is still a nascent idea in Technical Writing. It encompasses everything; structured authoring, topic-based writing, information mapping, and minimalism.

Most documents I aim to author in the future will be smaller in size and still independent. It will be a unit in itself, and almost every page is a unit in itself. The document will have very few external dependencies. Any variables used in it will be local variables and not global variables. Richly linked with suggested topics, books, and articles, it will be a part of the whole and still independent.

Every page is page one (EPPO) topic aims to allow readers to read in any order beginning from anywhere. It is easy to gather feedback and measure the usefulness of an EPPO topic. Imagine that you have 1000 page document and the customer is not happy, and it will be difficult for you to figure out the source of this unhappiness.

EPPO is Just like the Agile methodology. It allows you to fail in a small way while aiming to win big. The conventional book structure is not as consistent with the agile processes of the current day. Technical Writing also needs to reinvent itself to be more agile.

Mark Baker pioneered the idea of EPPO. It applies to writing for the web as well as offline documents.

The ability to learn is the key to survival. We can learn faster by learning from each other.

Comments

Popular posts from this blog

YAML front matter in Typora

Technical Writing essentials

Apply Goldilocks principle