Write overview documentation

[rhiaro]

In this first iteration, this documentation should cover information that is unique to the DRT (i.e. we should assume that the developer knows Python, Django, JSON Schema, OCDS, etc. which are not unique to the DRT). It should cover the information that developers newly working on the DRT would be given, with respect to the responsibilities of each component (lib-cove-ocds, lib-cove, cove-ocds, cove), for example.

Related reading:

• General CoVE docs
• OCDS tools
• ocdskit
• lib-cove-ocds

Possible contents:

• Internal architecture of cove-ocds (where to find code for what)
• Connection with external libs
• How to add an additional check
• Translations
• The CLI
• Template structure
• Something about extensions

[rhiaro]

Write overview documentation for the DRT

[ColinMaudry]

Chapter 1: what does DRT stand for?

:wink:

[jpmckinney]

Some notes by @Bjwebb on:

• How to add headlines
• How to modify validation error messaging

https://docs.google.com/document/d/1EER_GjXi7F0SPZ_Mra9JuQBY5JxU0NGRSS9mYzB4guU/edit