Patrick.Sy/website-and-documentation
1
0
Fork 0
forked from DevFW-CICD/website-and-documentation
Code Pull requests Activity

doc(onboarding): more text for conclusio

Browse source
This commit is contained in:
Stephan Lo 2024-09-15 22:59:17 +02:00
parent ffeb426d32
commit 63e809b719
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
content/en/docs/project/onboarding/conclusio/_index.md
View file

@ -8,10 +8,17 @@ weight: 1
We come along from a quite well known, but already complex discipline called 'Platform Engineering', which is the next level devops.
On top of these two domains we now have 'Framework Engineering', i.e. buildung dynamic, orchestrated and reconciling platforms:
| | | |
| Classic Platform engineering | New: Framework Orchestration on top of Platforms | Your job: Framework Engineer |
| -- | -- | -- |
| <img src="./images/layers-and-platform-engineer.png" width="200"> |<img src="./images/layers.png" width="200"> | <img src="./images/layers-and-framework-engineer.png" width="200"> |
## The whole picture of engineering
So always keep in mind that as as 'Framework Engineer' you
* include the skills of a platform and a devops engineer,
* you do Framework, Platform and Devops Engineering at the same time
* and your results have impact on Frameworks, Platforms and Devops tools, layers, processes.
The following diamond is illustrating this: on top is you, on the bottom is our baseline 'DevOps'
<img src="./images/modern.png" width="600">