Epic: Porter Docs v2 Strategy

[phillipgibson]

What design is being proposed? v2 documentation strategy that is more operations focused, as well as easily consumable for developers/operators to contribute.

Additional Context This will be a redesign of the current documentation to look at the possibility of rebranding components as well as promoting the brand awareness of around the bundles concept.

Risks/Concerns Currently there are opinions that Porter suffers from a misunderstanding in the IaC operators community. Providing more clear use cases and integrations with other tooling will help demystify Porter as a competing deployment mechanism to other IaC tools.

What other approaches were considered? A new documentation ToC has been agreed upon to help with the flow of content. The v2 design will be a more durable layout of the content to build upon for future features and content.

Implementation details TBD

Checklist

• [ ] An announcement of this proposal has been sent to the Porter mailing list: https://getporter.org/mailing-list NOTE - this was discussed on the 6/29/23 community call
• [ ] This proposal has remained open for at least one week, to allow time for community feedback.

Current Document Issues to be resolved

• [x] Docs - create-bundle.md update
• [x] Docs - intro-invocation-images.md update
• [x] Docs - what-is-porter.md update