35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
- Highest-level in the document structure
|
|
- Organized differently depending on work or home
|
|
- Different templates depending on work or home, and within that the specific type of project
|
|
- Is applied to a folder
|
|
|
|
## Project Properties
|
|
→ Title
|
|
→ Date Created
|
|
→ Date Due
|
|
→ Description
|
|
→ Priority ⇒ 0 (lowest) through 9 (highest)
|
|
→ Status ⇒ Not Started, Waiting, In Progress, Done
|
|
→ Type : Project
|
|
→ Project Lead {Work Only}
|
|
→ Charge Code {Work Only}
|
|
→ OneDrive Link {Work Only}
|
|
→ Shared Area Link {Work Only}
|
|
→ Git Repo {Personal Only}
|
|
→ Nextcloud Link {Personal Only}
|
|
|
|
## General Structure of Document
|
|
→ Scope and Description
|
|
A writeup about what the project is about, it's goals are, who the customer is, and any relevant details. This is an elaboration on the description property.
|
|
→ [[2.1 Tasks|Tasks]]
|
|
A base that contains the tasks of the project. A task is broadly defined as a distinct component of a project that, at the conclusion, produces a result that is needed an an input to another task or an output of the whole project.
|
|
→ [[2.2 Deliverables|Deliverables]]
|
|
A base that contains a list of the final outputs of the project. This exists so that notes can be made regarding each individual output, and so that the progress towards a certain output can be tracked.
|
|
→ [[2.3 Resources|Resources]]
|
|
A base that contains all the resources of a project, so that they can be easily access from one place instead of having to deep-dive into specific tasks to find it. This section will also contain the metabind buttons to add each resource type.
|
|
|
|
## General Structure of Folder
|
|
#todo This
|
|
|
|
## Creating the Project
|