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.
|
||||
@@ -10,4 +9,4 @@ It has a huge community, so it's no wonder it's among the top 10 CMS worldwide i
|
||||
|
||||
At AOE we consume Drupal mainly headless via JSON API. We appreciate its large feature set and mature plugin system as well as the general ecosystem.
|
||||
|
||||
In addition, the extensive documentation and setup with [DDEV](/tools/ddev/) make it easy to get started.
|
||||
In addition, the extensive documentation and setup with [DDEV](/tools/ddev/) make it easy to get started.
|
||||
|
||||
@@ -1,11 +1,10 @@
|
||||
---
|
||||
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.
|
||||
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.
|
||||
|
||||
Figma puts together all of the features we used in different tools (Axure, Miro, Abstract, Sketch, Anima, Invision) in one. It allowed us to make a single source of truth for our products, create design systems, and eliminate the vast majority of the pain points we faced in the past. It became beneficial, especially in remote and distributed design work, and speed up all our design-related processes. In addition to its real-time design and collaboration capabilities, Figma also offers an extensive, community-backed plugin collection and a robust API that helps to improve the DesignOps processes.
|
||||
|
||||
@@ -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.
|
||||
@@ -13,4 +12,4 @@ At AOE, we are currently taking our first steps with NX in a mono repo that is h
|
||||
The integration with the Node.js components (React, Next.js, Cypress) works smoothly and brings the expected benefits such as faster build times through intelligent caching.
|
||||
Support for Go is currently only rudimentary, which is why NX still has to prove itself in this area.
|
||||
|
||||
Especially in the environment of Node.js in combination with the use of a mono repo, NX is worth a look.
|
||||
Especially in the environment of Node.js in combination with the use of a mono repo, NX is worth a look.
|
||||
|
||||
@@ -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/).
|
||||
@@ -16,4 +16,4 @@ C/C++ code/libraries can be integrated by its [binding generator tool](https://g
|
||||
At stackoverflow it is votes 5 years in a row ([2016](https://insights.stackoverflow.com/survey/2016#technology-most-loved-dreaded-and-wanted), [2017](https://insights.stackoverflow.com/survey/2017#technology-_-most-loved-dreaded-and-wanted-languages), [2018](https://insights.stackoverflow.com/survey/2018#technology-_-most-loved-dreaded-and-wanted-languages), [2019](https://insights.stackoverflow.com/survey/2019#technology-_-most-loved-dreaded-and-wanted-languages), [2020](https://insights.stackoverflow.com/survey/2020#technology-most-loved-dreaded-and-wanted-languages-loved)) for the `most loved programming-language` by programmers.
|
||||
The [popularity](https://insights.stackoverflow.com/survey/2020#technology-most-loved-dreaded-and-wanted-languages-loved) is growing continuous.
|
||||
|
||||
With it's memory-safety/efficiency and energy-efficiency it helps to save money for bug-fixing, energy and cloud-computing.
|
||||
With it's memory-safety/efficiency and energy-efficiency it helps to save money for bug-fixing, energy and cloud-computing.
|
||||
|
||||
@@ -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.
|
||||
@@ -18,7 +18,7 @@ It's not just a small iteration on Scala 2 but a complete overhaul of the langua
|
||||
* Providing type-class instances via `given`
|
||||
* direct extension method syntax `extension (s: String) def pirate: String = s"$s arr!"`
|
||||
* Type System improvements
|
||||
* `enum`s
|
||||
* `enum`s
|
||||
* opaque types
|
||||
* intersection and union types
|
||||
* dependent function types
|
||||
@@ -30,4 +30,4 @@ It's not just a small iteration on Scala 2 but a complete overhaul of the langua
|
||||
|
||||
Even with these big changes Scala 3 provides a great compatibility story supporting Scala >2.13.5 libraries in Scala 3 projects and vice versa.
|
||||
|
||||
Although slowly we will update our existing Scala 2 codebase to Scala 3 over the next months and years to take advantage of the improvements made.
|
||||
Although slowly we will update our existing Scala 2 codebase to Scala 3 over the next months and years to take advantage of the improvements made.
|
||||
|
||||
@@ -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,
|
||||
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