Article ۰ Body

The Body represents a basic block. Each Body is self-contained and holds all the data required for rendering within its data structures.

Common use cases for this are Type.BODY where the textual article body can be found and the TYPE.ARTICLE_SOURCE where onward articles are referenced.

message Body {
repeated BodyNode children = 1;
Type type = 2;

[~]

Type

Each Body has a Body.Type to help the consumer to correctly interpret the BodyNode's content.

enum Type {
TYPE_UNSPECIFIED = 0;
BODY = 1;
ARTICLE_SOURCES = 2;
DISCLAIMER = 3;
TRUST_BOX = 4;
TABLE_OF_CONTENTS = 5;
}

[~]

BodyNode

Recursive structure representing all types of possible nodes inside an article.

One use-case is to represent HTML-like markup in tapir, but it is also used to map custom elements that require a strict positional placement within the textual body. Things that are not part of the textual article body are represented as individual Body parts so they can be rendered independently if required.

Clients must be resilient to unknown or missing nodes.

message BodyNode {
string type = 1;
string text = 2;
map<string, string> fields = 3;
repeated BodyNode children = 4;
repeated Element elements = 5;
}

[~]

fields

HTML like

Custom

[~]