| id | title | sidebar_label | scopetag | date |
|---|---|---|---|---|
man-usr-repo |
Using Markdown files in a Git Repo |
Using Git Repo Markdown |
tev2 |
20220513 |
import useBaseUrl from '@docusaurus/useBaseUrl'
:::caution
The entire section on Terminology Engine v 2 (TEv2) is still under construction.
As TEv2 is not (yet) available, the texts that specify the tool are still 'raw', i.e. not yet processed.
readers will need to see through some (currently unprocessed) notational conventions.
:::
One way in which curators may decide that users can contribute, is by enabling them to create pull requests to the repository that contains the scope's corpus. The curators SHOULD specify the procedures, the code of conduct, etc. that support and enable the maturing of these texts, and how it is decided that such texts can become part of the scope's corpus. That's outside the scope of this document.
From the TEv2 perspective, users contribute by creating and changing the markdown pages that describe the various terminological artifacts, such as concepts , use-cases, mental models, etc.
A user can use term refs to mark the terms that it wants to be linked to a specific meaning (terminological aritfact).
:::note Editor's note: Text has to be provided here :::