---
id:
aliases: []
tags:
  - topic/automation
  - topic/organization
  - topic/software
  - status/fleeting
---
# Automating Estimating Project Creation

Use-case specific wrapper for a document database like MongoDB.

## Features

Features below are in addition to those of Vanilla Atlas.

### Extract from Bid Boards

```sh
> jobHandler --new project --from-web https://app.buildingconnected.com/opportunities/66fab32654ef4e1affd178e0/info
...
```

```sh
> jobHandler --select project freezpak
jobHandler\FreezPak Cold Storage> --add-details --from-web https://app.buildingconnected.com/opportunities/66fab32654ef4e1affd178e0/info
...
```

## Standard Structured Text for Projects

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.
