Rework what is a build pipeline page

[John Libby]

• 10k foot view - ten thousand
• 1st diagram should start with new idea instead of work goes into production - boxley agrees, try out mermaid.js, boxley to send link
• "How do me and my fellows be happy about the work that we do?" - needs to be reworded
• 2nd diagram should start with "write some code" - agreed
• do we want to assume TDD practices here? no
• Why does it say there is too much detail? probably not needed
• "discusssed" - just fix
• "yep, this is vague" - reword
• mention containerization, very important
• the part where definition of build pipeline begs other questions feels scattered and unwieldy, also a distraction/segue. Maybe just move up?
• "Let's break that up into more detail:" image: maybe put an arrow from left to right indicating direction process will go through? yes
• I'd like to see these diagrams have borders and a background color yes
• Need to break up pyramid section into smaller chunks yes
• Too many diagrams/points of view on this page. Where are we going with all this? Have we defined what a build pipeline looks clearly? yes
• Work on cycle time section. There are duplicate images and text needs to be integrated into the flow of the page