documentation: Add tags to all featured blibs (#139)
* documentation: add tags to all featured blips
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
title: "API-First Design Approach"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [architecture]
|
||||
---
|
||||
|
||||
The API of any software we develop shapes in which way developers, teams, customers and users interact with our software.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Argo CD"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [ci/cd]
|
||||
---
|
||||
|
||||
We've been managing the state of application deployments in YAML files via Git repositories in the past. But we still wouldn't call this GitOps. A lot of custom glue code and tools were involved. While [helmfile](https://github.com/roboll/helmfile) replaces some of our custom tooling in a nice way we've also been trying a new approach with [Argo CD](https://argoproj.github.io/cd/).
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "AWS Fargate"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
It doesn't always have to be Kubernetes. For projects with a small number of applications launching and managing a Kubernetes cluster might be just too much. AWS Fargate is a nice alternative for running your containerized applications. Everything can be provisioned via Terraform and AWS Fargate, which allows you not having to deal with clusters or nodes abstracting everything away from you.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "backstage"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [documentation, agile]
|
||||
---
|
||||
|
||||
We see a lot of clustering in teams, microservices, libraries, and so on. We think a centralized software catalog
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Bare.ID"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [devops, security]
|
||||
---
|
||||
|
||||
[Bare.ID](https://bare.id) is our solution to the problem of operating and maintaining a [Keycloak](https://keycloak.org) cluster: a SaaS offering for a managed Keycloak cluster.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "DGS Framework"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [frontend, architecture]
|
||||
---
|
||||
|
||||
DGS has proven to simplify the development of GraphQL server applications.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "GitLab"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [ci/cd, coding]
|
||||
---
|
||||
|
||||
We merged GitLab and GitLab CI, because we use the whole tool as one, with all the integrations between the different sections. CI is just one of them.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Inner Source"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
tags: [agile]
|
||||
---
|
||||
|
||||
Inner Source is a strategy to frictionless cross-team collaboration in software development inside an organization.
|
||||
|
||||
@@ -2,9 +2,10 @@
|
||||
title: "Lighthouse CI"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [ci/cd, frontend]
|
||||
---
|
||||
At AOE, we want to keep a permanent eye on the metrics of the [Web Vitals](https://web.dev/learn-web-vitals/) for our projects.
|
||||
|
||||
[Lighthouse CI](https://web.dev/lighthouse-ci/) is a collection of free tools that facilitate the use of Lighthouse for performance monitoring. With Lighthouse CI we get a history of evaluation results and can compare them over time. It is also possible to set performance budgets to ensure that a website's performance does not deteriorate through regression.
|
||||
|
||||
Although performance monitoring is the most common use case for Lighthouse CI, other aspects of Lighthouse can also be monitored, such as SEO or accessibility. Thus, the use of Lighthouse CI can help ensure an overall good user experience.
|
||||
Although performance monitoring is the most common use case for Lighthouse CI, other aspects of Lighthouse can also be monitored, such as SEO or accessibility. Thus, the use of Lighthouse CI can help ensure an overall good user experience.
|
||||
|
||||
@@ -3,4 +3,7 @@ title: "Loki"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
featured: true
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
Updated to adopt.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Mob Programming"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
tags: [agile, coding]
|
||||
---
|
||||
|
||||
While practising pair programming for several years now at AOE, we have started using
|
||||
|
||||
@@ -3,6 +3,7 @@ title: "Monorepo"
|
||||
ring: trial
|
||||
quadrant: methods-and-patterns
|
||||
featured: true
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
A monorepo is a single repository containing multiple projects and shared libraries with their relationships.
|
||||
|
||||
@@ -3,6 +3,7 @@ title: "No-Code / Low-Code"
|
||||
ring: assess
|
||||
quadrant: methods-and-patterns
|
||||
featured: true
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
No-code or low-code refers to tools that allow application software to be created via graphical user interfaces and configuration - instead of (classic) text-based programming.
|
||||
|
||||
@@ -3,6 +3,7 @@ title: "NX"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: true
|
||||
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
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Pipeline as Code"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
In the past years many tools have evolved and especially [Gitlab CI](https://docs.gitlab.com/ee/ci/), [Github Actions](https://github.com/features/actions) and [AWS CodeDeploy](https://aws.amazon.com/de/codedeploy/) matured or became available and widely used across many teams.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Playwright"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [coding, frontend, quality assurance]
|
||||
---
|
||||
|
||||
Playwright is a cross browser/platform/language tool to write reliable end-to-end tests. It waits for elements before performing any actions which eliminates the need for timeouts - the primary cause of flaky tests.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Remix"
|
||||
ring: trial
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
Remix is a full stack web framework that lets us focus on the user interface and work with web standards.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Renovate"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [ci/cd]
|
||||
---
|
||||
|
||||
At AOE, we rely on [Renovate CLI tool](https://www.npmjs.com/package/renovate/) in the CI pipelines for most of our projects.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Resilience Thinking"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [architecture]
|
||||
---
|
||||
|
||||
Resilience is the capability of an application or service to resist different error scenarios. Especially for distributed systems - where a lot of communication between different services happen - it's very important to explicitly think of implementing resilience.
|
||||
|
||||
@@ -3,6 +3,7 @@ title: "Scala 3"
|
||||
ring: "adopt"
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
Following up on the previous 'trial' we will move our existing Scala codebase to
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Semanticore"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [ci/cd, documentation, quality assurance]
|
||||
---
|
||||
|
||||
[Semanticore](https://github.com/AOEpeople/semanticore) is an open source tool fulfilling our needs for managing changelogs and semantic releases.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "SonarQube"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [ci/cd, quality assurance]
|
||||
---
|
||||
|
||||
To track code quality of our projects and check for security issues (Static Application Security Testing), we recommend
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Spock + Geb"
|
||||
ring: hold
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, quality assurance]
|
||||
---
|
||||
|
||||
[spockframework.org](http://www.spockframework.org) - Spock is a testing and specification framework for Java and Groovy applications.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Spring REST Docs"
|
||||
ring: hold
|
||||
quadrant: tools
|
||||
tags: [documentation]
|
||||
---
|
||||
|
||||
[Spring REST Docs](https://spring.io/projects/spring-restdocs/) auto generates [Asciidoctor](http://asciidoctor.org/) snippets with the help of [Spring MVC Test](http://docs.spring.io/spring/docs/current/spring-framework-reference/htmlsingle#spring-mvc-test-framework) or [RestAssured](https://www.aoe.com/techradar/tools/rest-assured.html).
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Stitches"
|
||||
ring: trial
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
Stitches is a lightweight & performant CSS-in-JS styling library with a focus on component architecture and developer experience.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Tailwind CSS"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
At AOE we use Tailwind now on several projects. From fast prototyping, over marketing websites to enterprise applications.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Unleash"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend, devops]
|
||||
---
|
||||
|
||||
[Unleash](https://www.getunleash.io/) is a feature (toggle / flag) management service written in Node.js.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Vault"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [devops, security]
|
||||
---
|
||||
|
||||
Secure handling of access tokens is key to provide secure applications and environments.
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
title: "Vistecture"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [documentation, architecture]
|
||||
---
|
||||
|
||||
[Vistecture](https://vistecture.me/) is a tool for the visualization and analysis of distributed
|
||||
|
||||
Reference in New Issue
Block a user