update

src/deployment.adoc

@@ -5,36 +5,38 @@ This is done via the classic Change and Transport System (CTS).
 
 === Deployment Process Overview
 
-something something
+Most steps of the deployment process are automated, if something fails this late in the process, something early in the process should be fixed to catch it.
 
 image::img/deployment.drawio.svg[align="center"]
 
-=== todo
+=== System SCI checks
 
-Auditing via classic CTS
+Static analysis feedback is provided to the developer already on the first push.
 
-Pre-production environment
+While on GitHub, the code only knows about the code, and not the structuring of the system, so additional SAP Code Inspector (SCI) checks can be performed on the system, eg. to check the package structure.
 
-Heliconia Labs will provide more tooling in this area in the future
+If there are any issues found in SCI, it should be used as feedback to improve the information provided to the developer in the development process.
 
-ATC/SCI to check eg. package structure
+=== Sequencing
 
-check branch is approved, up to date + ok status checks
+Developments have dependencies, sometimes these are not already in production.
 
-release override feature
+This can be discovered already in the pull request during development, eg. via the abaplint.app cross check or parallel changes feature.
 
-badi `CTS_REQUEST_CHECK`, `CHECK_BEFORE_RELEASE`
+To help checking the SAP standard transaction `/SDF/TRCHECK` can be used.
 
-irreversible changes, eg. DDIC => abaplint.app feature / warning
+And for final verification, the transport is imported into the `STG` system, just previously to importing into the `PRD` system.
 
-=== Sequencing
+// todo, Heliconia Labs will provide more tooling in this area in the future
 
-txn `/SDF/TRCHECK`
+=== Rollback
 
-finding possible sequence issues early => abaplint.app feature
+Transports can be rolled back by creating an additional transport with the same contents. These can be created from the abapGit flow screen.
 
-feedback loop, if something fails late in the process, something early in the process should be fixed to catch it
+// todo, implement rollback feature
 
-=== Rollback
+// todo, BAdI `CTS_REQUEST_CHECK`, `CHECK_BEFORE_RELEASE`
+
+// todo, reconciliation ?
 
-rollback feature
+// todo, irreversible changes, eg. DDIC => abaplint.app feature / warning

src/index.adoc

@@ -19,6 +19,6 @@ include::development.adoc[]
 
 include::deployment.adoc[]
 
-<<<
+// <<<
 
-include::setup.adoc[]
+// include::setup.adoc[]

src/introduction.adoc

@@ -45,9 +45,9 @@ The repository setup can be adjusted along the way, to fit the needs of the deve
 
 Works on most SAP ABAP on-prem systems, upgrade tooling at any time, no need to wait for SAP to release new features. No need to upgrade to newest S/4 HANA to get the latest development tools.
 
-*Modular monolith approach*
+// *Modular monolith approach*
 
-_todo, write Blog post about this_
+//_todo, write Blog post about this_
 
 *Keeping the core moving*
 
@@ -88,21 +88,19 @@ For product/add-on development which is typically released as a whole, instead o
 
 === Nuve Platform
 
-_todo_
+Nuve Platform provides de-central development systems, and automated unit testing in real systems in a continuous integration setup.
 
 link:https://www.nuveplatform.com[Nuve Platform]
 
-Unit testing feedback in a continuous integration setup and decentralized development
-
 === abaplint.app
 
-_todo_
+abaplint.app provides fast configurable static analysis of ABAP code, with code insights and statistics.
 
-link:https://abaplint.app[abaplint.app]
+Configuration is versioned and changed like code, any developer can suggest changes and changes are reviewed before being merged.
 
-Static analysis of ABAP code, helping reminding developers of best practices and common mistakes.
+All developers have access to insights and statistics, without additional infrastructure setup or maintenance.
 
-Code insights and statistics
+link:https://abaplint.app[abaplint.app]
 
 === Example landscape
 

src/process.adoc

@@ -1,3 +1,5 @@
 == End to End Process
 
+There are many steps in the end-to-end process, however, users are guided through the steps via tooling and automation.
+
 image::img/process.drawio.svg[align="center"]