docs: clean up blip headers
This commit is contained in:
committed by
Stefan Rotsch
parent
84d5939770
commit
88801e6e93
@@ -1,15 +1,14 @@
|
||||
---
|
||||
title: "Monorepo"
|
||||
ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
featured: true
|
||||
tags: [coding]
|
||||
title: "Monorepo"
|
||||
ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
A monorepo is a single repository containing multiple projects and shared libraries with their relationships.
|
||||
|
||||
At AOE, we are using a monorepo that is home to both our React and Next.js based frontends and
|
||||
our [Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backends,
|
||||
At AOE, we are using a monorepo that is home to both our React and Next.js based frontends and
|
||||
[Go](/languages-and-frameworks/go-lang/) / [Flamingo](/languages-and-frameworks/flamingo/) based backends,
|
||||
as well as shared libraries we use in all of our projects.
|
||||
|
||||
The main benefits in that approach are:
|
||||
@@ -18,5 +17,5 @@ The main benefits in that approach are:
|
||||
* Same CI Setup for everything and no overhead on new projects
|
||||
* Tool consistency over all projects
|
||||
|
||||
If you take the monorepo approach, of course you want to have a tool to manage it. There are a lot of them on the market
|
||||
If you take the monorepo approach, of course you want to have a tool to manage it. There are a lot of them on the market
|
||||
and at AOE we have decided to go with [Nx](/tools/nx/).
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "No-Code / Low-Code"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
featured: true
|
||||
tags: [coding]
|
||||
title: "No-Code / Low-Code"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
No-code or low-code refers to tools that allow application software to be created via graphical user interfaces and
|
||||
|
||||
@@ -1,11 +1,8 @@
|
||||
---
|
||||
title: "NX"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: true
|
||||
tags: [coding, ci/cd]
|
||||
title: "NX"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [coding, ci/cd]
|
||||
---
|
||||
|
||||
[Nx](https://nx.dev/) is now a daily used tool in our Monorepo setup. It takes care of everything from app creation to
|
||||
running development environments and tests to code generation.
|
||||
|
||||
[Nx](https://nx.dev/) is now a daily used tool in our Monorepo setup. It takes care of everything from app creation to running development environments and tests to code generation.
|
||||
|
||||
@@ -1,11 +1,8 @@
|
||||
---
|
||||
title: "Scala 3"
|
||||
ring: "adopt"
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
tags: [coding]
|
||||
title: "Scala 3"
|
||||
ring: "adopt"
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
Following up on the previous 'trial' we will move our existing Scala codebase to
|
||||
Scala 3 where possible. Some Frameworks like Play will need some time to allow
|
||||
us moving but for our smaller services a migration is possible.
|
||||
Following up on the previous 'trial' we will move our existing Scala codebase to Scala 3 where possible. Some Frameworks like Play will need some time to allow us moving but for our smaller services a migration is possible.
|
||||
|
||||
Reference in New Issue
Block a user