> For the complete documentation index, see [llms.txt](https://docs.envisioning.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.envisioning.io/methodology/phases-of-study/5.-describe.md).

# 5. Describe

Updating and creating new technology descriptions

Once the [technologies](/technology-card.md) are approved and refined by the research team, they are ready to be updated and fully developed. 

{% hint style="info" %}
During this stage, researchers are able to check the selected technologies on the "Update/Create \[Researchers]" list of the Workflow board.
{% endhint %}

### Update Technologies

In order to update technologies, researchers should follow the steps below:

* [ ] Add at least two new [sources](broken://pages/-LyV9AfGtx1iNQOK12Hb) (less than 6months old)
* [ ] Review if the technology card is following the latest [technology standards](broken://pages/-LyV95rZgl4secUBj9PX)
* [ ] Add new relevant information
* [ ] Add at least three new organizations (if possible)
* [ ] Review technology [image](broken://pages/-LyV9D6HGoAeLepI84We)
* [ ] Review technology's [TRL score](broken://pages/-Ly13oz0KHbvrqGAN595)
* [ ] Drag technology card to "Edit \[Editor]" list on the workflow board

{% hint style="danger" %}
Only technologies that have been thoroughly edited by the researchers should be dragged to the Editor's stash. It should include a complete title, summary, description, and the update of attachments and organizations.
{% endhint %}

### Describe new technologies

In order to describe new technologies, researchers should study carefully at least two of our latest projects in order to understand our expectations and to use it as a work reference. All entries on TDB (Technology Database) stick to basic standards to keep and maintain an editorial line, and are expected to follow the standards listed below:

{% content-ref url="/pages/-LyV95rZgl4secUBj9PX" %}
[Broken mention](broken://pages/-LyV95rZgl4secUBj9PX)
{% endcontent-ref %}

{% content-ref url="/pages/-LyV9AfGtx1iNQOK12Hb" %}
[Broken mention](broken://pages/-LyV9AfGtx1iNQOK12Hb)
{% endcontent-ref %}

{% content-ref url="/pages/-LyV9Fwfqof0uhuoNI99" %}
[Broken mention](broken://pages/-LyV9Fwfqof0uhuoNI99)
{% endcontent-ref %}

{% content-ref url="/pages/-LyV9D6HGoAeLepI84We" %}
[Broken mention](broken://pages/-LyV9D6HGoAeLepI84We)
{% endcontent-ref %}

{% hint style="info" %}
During this stage, technologies are marked as "Draft" and they should remain so until the editor work on its description and change it's status to "Review". Only when the final reviewer approve the technologies they should be changed to "Published". Therefore, only editors and reviewers are allowed to change their status throughout our process. <br>
{% endhint %}

## Tone

Envisioning's writing style is as didactic as possible without taking out complexity. Our readers are not experts, neither they are completely numb to our object of study. A few tips that can help researchers and editors to achieve that are:

| Do                                                                                                                                                                                 | Don’t                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Avoid the passive voice</li><li>Use short sentences</li><li>Use synonyms</li><li><p>When possible, cite:</p><ul><li>Statistics</li><li>Science fiction</li></ul></li></ul> | <ul><li>Never copy+paste from sources, create a fully original description</li><li>Do not start the description with technology name, unless it is an alternative name</li><li>Do not start the description with "it is", "this is", etc. </li><li>Do not mention organizations (labs, companies, start ups) at the description</li><li>Do not be assertive about the future, use terms such as "it might", "it probably will", etc.</li></ul> |

{% hint style="danger" %}
The technology's description is only a part of the "technology card" on TDB. Therefore, researchers must not refer to organizations or the technology's TRL at the description, simply because every feature of the whole structure design has its own field to be completed (e.g. TRL, Lenses, etc.)
{% endhint %}

## TDB Tutorial

* [ ] Enter TDB
* [ ] Click \[Add Technology]
* [ ] Enter Title information following the directions of this manual
* [ ] Click \[Create]
* [ ] Enter information following the directions of this manual
* [ ] Click \[Enter]
* [ ] Click \[Projects]
* [ ] Select the project that requires the technology
* [ ] Go to the Workflow board
* [ ] Drag technology card to Edit list

{% embed url="<https://youtu.be/1nrfD8oon2E>" %}