---
tags:
  - destiny/fleeting
  - topic/automation
  - topic/estimating
  - type/idea
title: Project Info
---
# Project Info

Standardize formatting and input methods for common
(mostly multi-family specific)
project info, including:

* levels by elevation
* unit types
    * info
    * by level
* area types by level
* switchgear by level
* feeders
    * from->to's with feeder tags
    * feeder tag definitions

To calculate regular quantities

* by feeder routing
  * sleeving
  * conductor support
* by area
  * temp power

Markdown with YAML frontmatter is an excellent choice for project documentation
which offers a compromise between interoperability and flexibility.

* [x] Create an `Import-Markdown` returning `frontmatter` and `body` objects.
* [ ] Create vscode workflows for formatting frontmatters and calculating properties.
* [ ] Integrate my "Estimating Work" and "Notebook" folders
  * Before my plaintext renaissance, I used to need many more .xlsx and .pdf files
    for a single project. It makes better sense for `Sources.xlsx` to be .yaml

Ultimately most project information could be formatted in markdown and yaml files,
greatly aiding in:

* quick research
* data aggregation and analysis
* version control and backups
* software independence

without compromising on professional output.
Even proposals are truly better suited to this format as,
neglecting the former benefits,
markdown can be rendered with standard stylesheets for improved consistency.

Sublime is a friendly option for non-technical users,
Obsidian even more so it seems,
however neither are free for commercial use.
