Removed bad practices guide

Author: danjoa

get-started/about.md

@@ -131,8 +131,6 @@ In general, we always propose that approach:
 >   3. loosely coupled, coarse-grained subsystems with separate lifecycles
 >  - **False** reasons are: distributed development, modularization, isolation, ... → there are well established and proven better ways to address these things, without the pain which comes with microservices.
 
-[See also the anti pattern of *Microservices Mania*](bad-practices#microservices-mania) {.learn-more}
-
 
 
 ### Parallelized Workflows
@@ -349,7 +347,6 @@ Of course, we also make mistakes and errors in CAP, but ...
 - And this effect increases with steadily growing adoption of CAP that we see, ...
 - And with the open culture we established successfully, for example, **open issue reports** in GitHub, that is, the standard out there, instead of private support tickets — a relict of the past.
 
-> Note that all of this is in contrast to code generators, where you can't fix code generated in the past → see also [*Avoid Code Generators*](bad-practices#code-generators) in the anti patterns guide.
 
 ### Minimized Lock-Ins
 
@@ -378,7 +375,7 @@ Keeping pace with a rapidly changing world of volatile cloud technologies and pl
 
 - AI provides tremendous boosts to productivity → for example:
   - **Coding Assists** → for example, by [GitHub Copilot](https://github.com/features/copilot) in `.cds`, `.js`, even `.md` sources
-  - **Code Analysis** → detecting [bad practices](bad-practices) → guiding to [best practices](best-practices)
+  - **Code Analysis** → detecting bad practices → guiding to [best practices](best-practices)
   - **Code Generation** → for example, for tests, test data, ...
   - **Project Scaffolding** → for quick head starts
   - **Search & Learning Assists** → like SAP Joule, ...

get-started/bad-practices.md

@@ -280,7 +280,6 @@ Don't confuse CAP services with Microservices:
 
 CAP services are important for how you *design* and *implement* your applications in clean and modularized ways on a fine-granular use case-oriented level. The primary focus of Microservices is on how to cut your whole application into independent coarse-grained(!) deployment units, to release and scale them independently.
 
-[Learn more about that in the *Anti Patterns* section on Microservices](bad-practices#microservices-mania) {.learn-more}
 
 ## Events
 
@@ -636,7 +635,6 @@ Not only do we address the very same goals, we can also identify several symmetr
 >
 > CAP is very much in line with both, the intent and goals of Hexagonal Architecture, as well as with the fundamental concepts. Actually, CAP *is an implementation* of Hexagonal Architecture, in particular with respect to the [*Adapters*](#protocol-adapters) in the outer hexagon, but also regarding [*Application Models*](#application-domain) and [*(Core) Domain Models*](#application-domain) in the inner hexagon.
 
-[Also take notice of the *Squared Hexagons* section in the Anti Patterns guide](bad-practices#squared-hexagons) {.learn-more}
 
 
 

get-started/best-practices.md

@@ -155,8 +155,7 @@ After the [initial setup](#setup), we recommend continuing as follows while you
 | 1 | [Introduction – What is CAP?](about)  | Learn about key benefits and value propositions.       |
 | 2 | [Bookshop by capire](in-a-nutshell)       | Build your first CAP application within 4-44 minutes.  |
 | 3 | [Best Practices](best-practices) | Key concepts & rationales to understand → *must read*. |
-| 4 | [Anti Patterns](bad-practices)   | Misconceptions & bad practices to avoid → *must read*. |
-| 5 | [Learn More](learning-sources)            | Find samples, videos, blogs, tutorials, and so on.     |
+| 4 | [Learn More](learn-more)            | Find samples, videos, blogs, tutorials, and so on.     |
 
 
 
@@ -173,4 +172,4 @@ After these getting started-level introductions, you would continuously revisit
 | 10 | [Resources](/resources/)                                                            | About support channels, community, ...         |
 
 
-This also reflects the overall structure of [this documentation](./learning-sources.md#this-documentation).
+This also reflects the overall structure of [this documentation](./learn-more#this-documentation).