---
# System prepended metadata
title: Task Management and Figma Version Control `v0.0.1`
---
---
type: slide
---
# Task Management and Figma Version Control `v0.0.1`
---
#### Video 1 - Tasks and information structure in the top level comment.
----
`@Info`
----
----
`@output` - Each issue must produce an output
----
`Multiple Outputs` - There may be cases of multiple outputs
----
`No Outputs` - Cases for no produced outputs
----
We put such tasks in closely related task group or in the `***Task Management Issue***`
----
`Indentation` - You must keep the @input & @output with the same hirerachy as the tasks listed within that group
---
#### Video 2 - `@inputs`, `@outputs`, next and their status
----
What is `@input`
----
`from` is to show the file destination
----
if produced in the same issue
----
then we don't use `from` tag to show destination
----
Mentioned previously, each task group produces an output
----
output destination
----
Link the comment where the worklog is presented
----
Such as the comment image below
----
`next` is use to show what task to work on after finishing this issue
----
Task status: `planned`, `in-progress` and `completed/done`
----
Planned -:question:
----
In-progress - :factory:
----
Completed - :package:
---
#### Video 3 - Worklog comment structure
----
----
----
----
----
----
----
----
----
----
----
----
----
----
----
----
Thank you
---
#### Video 4 - Version Control on Figma
----
----
----
----
----
----
----
----
----
----
----
----
----
----
----
----
----
What if you delete, split or deprecate a component?
----
----
----
----
----
Thank you
---
#### Video 5 - Connecting Github and Figma
----
----
----
----
----
----
----
----
----
----
----
----
Thank you