docs: clean up blip headers
This commit is contained in:
committed by
Stefan Rotsch
parent
84d5939770
commit
88801e6e93
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "DDEV"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: true
|
||||
tags: [coding, ci/cd]
|
||||
title: "DDEV"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [coding, ci/cd]
|
||||
---
|
||||
|
||||
[DDEV](https://www.ddev.com/ddev-local/) is an open source tool that makes it dead simple to get local PHP development environments up and running within minutes.
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
title: "Drupal"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
featured: true
|
||||
title: "Drupal"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
---
|
||||
|
||||
[Drupal](https://www.drupal.org/) is an open source content management system and framework based on a PHP stack.
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "Figma"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: true
|
||||
tags: [frontend, ux/ui, agile]
|
||||
title: "Figma"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [frontend, ux/ui, agile]
|
||||
---
|
||||
|
||||
Figma became our go-to tool for the next generation collaborative design. It allowed UX/UI designers, engineers, stakeholders, product managers, and other roles to view, inspect and comment on designs and wireframes, create high- and low-fidelity prototypes, and much more.
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "NATS"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
featured: true
|
||||
tags: [architecture, devops]
|
||||
title: "NATS"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [architecture, devops]
|
||||
---
|
||||
|
||||
[NATS](https://nats.io/) is a cloud native messaging and stream-data system for modern distributed software systems.
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
---
|
||||
title: "NX"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
featured: true
|
||||
title: "NX"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
---
|
||||
|
||||
[Nx](https://nx.dev/) is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "Rust"
|
||||
ring: "assess"
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
title: "Rust"
|
||||
ring: "assess"
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
[Rust](https://www.rust-lang.org/) is a young and modern programming language initially developed by [Mozilla Research](https://research.mozilla.org/).
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "Scala 3"
|
||||
ring: "trial"
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
title: "Scala 3"
|
||||
ring: "trial"
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
[Scala 3](https://docs.scala-lang.org/scala3/) is the successor of the Scala 2.x series programming language.
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "Sketch"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: true
|
||||
tags: [ux/ui]
|
||||
title: "Sketch"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [ux/ui]
|
||||
---
|
||||
|
||||
Figma is a vector graphics editor and primarily web-based prototyping tool, with additional offline features enabled by desktop applications for macOS and Windows. The Figma Mirror companion apps for Android and iOS allow viewing Figma prototypes on mobile devices. The next step in our toolchain development comes right after the Sketch+Abstract approach. Figma enabled the next level of collaboration between designers, stakeholders, and frontend engineers.
|
||||
|
||||
@@ -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,
|
||||
[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:
|
||||
|
||||
@@ -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