docs: fix spellcheck errors
This commit is contained in:
Stefan Rotsch
Bastian
@@ -2,11 +2,15 @@
|
||||
title: "Ansible"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [devops]
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
[Ansible](https://www.ansible.com/) is a tool used to describe infrastructure and applications and their configuration as code. It covers both the configuration and provisioning aspects of infrastructure and applications.
|
||||
[Ansible](https://www.ansible.com/) is a tool used to describe infrastructure and applications and their configuration
|
||||
as code. It covers both the configuration and provisioning aspects of infrastructure and applications.
|
||||
|
||||
It is a radically simple IT automation system based on SSH so that it can work without agents or exposed APIs. It handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation, and multi-node orchestration.
|
||||
It is a radically simple IT automation system based on SSH so that it can work without agents or exposed APIs. It
|
||||
handles configuration management, application deployment, cloud provisioning, ad-hoc task execution, network automation,
|
||||
and multi-node orchestration.
|
||||
|
||||
It comes in handy when the client currently uses some virtual machines with docker/docker-compose, and no full-blown Kubernetes cluster is available or needed.
|
||||
It comes in handy when the client currently uses some virtual machines with docker/docker-compose, and no full-blown
|
||||
Kubernetes cluster is available or needed.
|
||||
|
||||
@@ -2,14 +2,14 @@
|
||||
title: "Apache APISIX"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [devops]
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
[Apache APISIX](https://apisix.apache.org/) is an open-source, high-performance API gateway, designed for
|
||||
microservices, cloud-native and container-based architecture. It provides a wide range of features to manage
|
||||
and secure API services:
|
||||
|
||||
- Scalablbility: Load balancing and routing, dynamic scaling
|
||||
- Scalability: Load balancing and routing, dynamic scaling
|
||||
- Performance: Fast and reliable, supports caching and rate limiting
|
||||
- Multi-Protocol Support: Supports HTTP, HTTPS, WebSockets and gRPC
|
||||
- Customization: Plugins for authentication, authorization and traffic management
|
||||
|
||||
@@ -2,6 +2,6 @@
|
||||
title: "Apollo Client"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [architecture]
|
||||
featured: false
|
||||
tags: [architecture]
|
||||
---
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "ZeroTrust"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [security, architecture]
|
||||
featured: false
|
||||
title: "ZeroTrust"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [security, architecture]
|
||||
featured: false
|
||||
---
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: "Client-Side Error Logging"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [architecture, frontend]
|
||||
tags: [architecture, frontend]
|
||||
---
|
||||
|
||||
Updated to adopt.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "Concourse"
|
||||
featured: false
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [ci/cd]
|
||||
title: "Concourse"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [ci/cd]
|
||||
featured: false
|
||||
---
|
||||
|
||||
@@ -2,9 +2,10 @@
|
||||
title: "C#"
|
||||
ring: adopt
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
C# is a statically, strongly typed and object-oriented language.
|
||||
After PHP and several JVM languages, we also have projects with C#. We value all features of this highly developed language.
|
||||
|
||||
After PHP and several JVM languages, we also have projects with C#. We value all features of this highly developed
|
||||
language.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: "DDEV"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
featured: false
|
||||
tags: [coding, ci/cd]
|
||||
title: "DDEV"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [coding, ci/cd]
|
||||
featured: false
|
||||
---
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
---
|
||||
title: "Design System"
|
||||
ring: trial
|
||||
quadrant: "methods-and-patterns"
|
||||
featured: true
|
||||
tags: [ux/ui, frontend, coding, architecture, documentation]
|
||||
title: "Design System"
|
||||
ring: trial
|
||||
quadrant: "methods-and-patterns"
|
||||
tags: [ux/ui, frontend, coding, architecture, documentation]
|
||||
---
|
||||
|
||||
A Design System is a collection of reusable design components,
|
||||
guidelines and standards that serve as the foundation for creating a consistent user experience across a product or a whole brand.
|
||||
A Design System is a collection of reusable design components, guidelines and standards that serve as the foundation for
|
||||
creating a consistent user experience across a product or a whole brand.
|
||||
|
||||
It helps to create a unified visual language, improve collaboration among design and development teams,
|
||||
and streamline the design and development process.
|
||||
It helps to create a unified visual language, improve collaboration among design and development teams, and streamline
|
||||
the design and development process.
|
||||
|
||||
Design Systems also increase the maintainability of the design of products, making it easier for teams to make updates and add new features over time.
|
||||
Design Systems also increase the maintainability of the design of products, making it easier for teams to make updates
|
||||
and add new features over time.
|
||||
|
||||
We are in the process to implement a design system in close cooperation with one of our customers.
|
||||
|
||||
|
||||
@@ -2,5 +2,6 @@
|
||||
title: "DGS Framework"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [frontend, architecture]
|
||||
featured: false
|
||||
---
|
||||
|
||||
@@ -2,27 +2,33 @@
|
||||
title: "GraphQL"
|
||||
ring: adopt
|
||||
quadrant: methods-and-patterns
|
||||
tags: [architecture]
|
||||
---
|
||||
|
||||
[GraphQL](https://graphql.org/) is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data.
|
||||
[GraphQL](https://graphql.org/) is a query language for your API, and a server-side runtime for executing queries by
|
||||
using a type system you define for your data.
|
||||
GraphQL isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
|
||||
|
||||
GraphQL was developed by Facebook around 2010 and released 2015.
|
||||
The main challenge it solves is to improve communication between browser and server on high dynamic web apps.
|
||||
|
||||
The advantages are:
|
||||
* schema and schema validation together with a useful type system
|
||||
* the client (browser) controls what data should be sent (data reduction)
|
||||
* with one request you can fetch "all" required data
|
||||
|
||||
Client side integration can be achieved using the [Apollo Client Framework](/tools/apollo-client.html) which easily integrates into
|
||||
- schema and schema validation together with a useful type system
|
||||
- the client (browser) controls what data should be sent (data reduction)
|
||||
- with one request you can fetch "all" required data
|
||||
|
||||
Client side integration can be achieved using the [Apollo Client Framework](/tools/apollo-client.html) which easily
|
||||
integrates into
|
||||
[React.js](/languages-and-frameworks/react.html) based frontends.
|
||||
|
||||
For [Spring Boot](https://spring.io/projects/spring-boot/) based backends [DGS](https://netflix.github.io/dgs/) provides a nice framework featuring:
|
||||
For [Spring Boot](https://spring.io/projects/spring-boot/) based backends [DGS](https://netflix.github.io/dgs/) provides
|
||||
a nice framework featuring:
|
||||
|
||||
- an annotation-based programming model for Spring
|
||||
- a test framework for writing query tests as unit tests
|
||||
- a [Gradle](https://gradle.org/) code generation plugin to create types from a GraphQL schema in Java or Kotlin
|
||||
|
||||
|
||||
The framework [Flamingo offers support for GraphQL](https://docs.flamingo.me/3.%20Flamingo%20Modules/graphql.html) and also Flamingo Commerce offers a full featured GraphQL API for e-commerce features. ([Example GraphQL Console for Commerce](https://demoshop.flamingo.me/en/graphql-console))
|
||||
The framework [Flamingo offers support for GraphQL](https://docs.flamingo.me/3.%20Flamingo%20Modules/graphql.html) and
|
||||
also Flamingo Commerce offers a full featured GraphQL API for e-commerce
|
||||
features. ([Example GraphQL Console for Commerce](https://demoshop.flamingo.me/en/graphql-console))
|
||||
|
||||
@@ -2,14 +2,13 @@
|
||||
title: "Harbor"
|
||||
ring: trial
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [devops]
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
[Harbor](https://goharbor.io) is a CNCF-graduated open-source container registry. We use it to host custom built container images
|
||||
from our projects. Key benefits for us are:
|
||||
|
||||
* Harbor automatically scans all container images with [Trivy](https://trivy.dev)
|
||||
* fine grained access control allows Harbor to be used in a multi-team environment
|
||||
* its extensive API allows easy adaption to custom needs, like retention policies
|
||||
* support for image signing with [Cosign](https://github.com/SigStore/cosign)
|
||||
[Harbor](https://goharbor.io) is a CNCF-graduated open-source container registry. We use it to host custom-built
|
||||
container images from our projects. Key benefits for us are:
|
||||
|
||||
- Harbor automatically scans all container images with [Trivy](https://trivy.dev)
|
||||
- fine-grained access control allows Harbor to be used in a multi-team environment
|
||||
- its extensive API allows easy adaption to custom needs, like retention policies
|
||||
- support for image signing with [Cosign](https://github.com/SigStore/cosign)
|
||||
|
||||
@@ -6,7 +6,7 @@ tags: [devops]
|
||||
---
|
||||
|
||||
At AOE, we have adopted [Helmfile](https://github.com/helmfile/helmfile) as a complementary tool to Helm. It is
|
||||
a declarative spec for deploying helm charts providing addtional functionality such as:
|
||||
a declarative spec for deploying helm charts providing additional functionality such as:
|
||||
|
||||
- Separation between environment specific and general values
|
||||
- Simplified secrets management with support for external applications, e.g. Vault
|
||||
|
||||
@@ -2,8 +2,7 @@
|
||||
title: "Hot Chocolate"
|
||||
ring: assess
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
tags: [coding]
|
||||
tags: [coding]
|
||||
---
|
||||
|
||||
[Hot Chocolate](https://chillicream.com/docs/hotchocolate/v12) is an open-source GraphQL server for .NET.
|
||||
|
||||
@@ -2,10 +2,11 @@
|
||||
title: "Java"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, backend]
|
||||
tags: [coding, backend]
|
||||
---
|
||||
|
||||
[Java](https://www.java.com) is a versatile and widely-used programming language.
|
||||
|
||||
It is scalable and platform-independent, making it the ideal choice for businesses looking to streamline their
|
||||
operations and reach a wider audience. With its broad library of tools, frameworks and modules, Java provides developers
|
||||
with the resources they need to create dynamic, feature-rich applications that can be easily integrated into existing
|
||||
|
||||
@@ -5,8 +5,11 @@ quadrant: platforms-and-aoe-services
|
||||
tags: [devops, security]
|
||||
---
|
||||
|
||||
For years we used LDAP Login mechanisms to authenticate our employees.
|
||||
For years, we used LDAP Login mechanisms to authenticate our employees.
|
||||
|
||||
While this worked as some kind of "single credential" model, it does not support extended Security features such as WebAuthN, Multifactor-Authentication, etc.
|
||||
While this worked as some kind of "single credential" model, it does not support extended Security features such as
|
||||
WebAuthN, Multifactor-Authentication, etc.
|
||||
|
||||
These we do prefer to use integrations using OpenID Connect into SSO solutions such as [Bare.ID](/platforms-and-aoe-services/bareid.html) or [Keycloak](/tools/keycloak.html), which provide proper authentication and federation for multiple identity sources.
|
||||
These we do prefer to use integrations using OpenID Connect into SSO solutions such
|
||||
as [Bare.ID](/platforms-and-aoe-services/bareid.html) or [Keycloak](/tools/keycloak.html), which provide proper
|
||||
authentication and federation for multiple identity sources.
|
||||
|
||||
@@ -1,15 +1,24 @@
|
||||
---
|
||||
title: "Playwright"
|
||||
ring: trial
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding, frontend, quality assurance]
|
||||
title: "Playwright"
|
||||
ring: trial
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding, frontend, quality assurance]
|
||||
---
|
||||
|
||||
Playwright is a cross browser/platform/language tool to write reliable end-to-end tests. It's easy to get started with and offers a broad variety of functionalities out of the box. Playwright supports Windows, MacOs and Linux and works with the most popular testing frameworks such as Jest, Mocha and Jasmine.
|
||||
The playwright configuration offers plenty of helpful options, for instance native mobile emulation of Chrome for Android and Safari for iOS. If needed playwright can be extended by BDD tools like Cucumber or SpecFlow to enable non-technical contributors to collaborate.
|
||||
[Playwright](https://playwright.dev) is a cross browser/platform/language tool to write reliable end-to-end tests. It's
|
||||
easy to get started with and offers a broad variety of functionalities out of the box. Playwright supports Windows,
|
||||
macOS and Linux and works with the most popular testing frameworks such as Jest, Mocha and Jasmine.
|
||||
The playwright configuration offers plenty of helpful options, for instance native mobile emulation of Chrome for
|
||||
Android and Safari for iOS. If needed playwright can be extended by BDD tools like Cucumber or SpecFlow to enable
|
||||
non-technical contributors to collaborate.
|
||||
|
||||
Playwright test are resilient. It waits for elements before performing any actions which eliminates the need for timeouts - the primary cause of flaky tests.
|
||||
Playwright test are resilient. It waits for elements before performing any actions which eliminates the need for
|
||||
timeouts - the primary cause of flaky tests.
|
||||
|
||||
Other than Cypress Playwright can interact with different origins and multiple tabs. Also you can create scenarios with different contexts to handle multiple users within one test. Contexts allow saving an authentication state to reuse it in other tests. By isolating tests within a seperate browser context for each test, the tests are fully independent, although reusing an authentication state. This prevents you from performing repetitive log-in operations in each test.
|
||||
Other than Cypress Playwright can interact with different origins and multiple tabs. Also, you can create scenarios with
|
||||
different contexts to handle multiple users within one test. Contexts allow saving an authentication state to reuse it
|
||||
in other tests. By isolating tests within a separate browser context for each test, the tests are fully independent,
|
||||
although reusing an authentication state. This prevents you from performing repetitive log-in operations in each test.
|
||||
|
||||
As Playwright is developed and maintained by Microsoft there are some great extensions for Visual Studio Code to develop, run and debug tests.
|
||||
As Playwright is developed and maintained by Microsoft there are some great extensions for Visual Studio Code to
|
||||
develop, run and debug tests.
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: "pnpm"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
featured: true
|
||||
title: "pnpm"
|
||||
ring: assess
|
||||
quadrant: tools
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
[pnpm](https://pnpm.io/motivation) is an alternative tool to manage your frontend dependencies. Unlike yarn 1 it manages all packages in a central place and
|
||||
creates symbolic links only inside the npm_modules of a project. This results in considerably less usage of disk space and reduces build-times, when a package
|
||||
is already available.
|
||||
[pnpm](https://pnpm.io/motivation) is an alternative tool to manage your frontend dependencies. Unlike yarn 1 it manages
|
||||
all packages in a central place and creates symbolic links only inside the npm_modules of a project. This results in
|
||||
considerably less usage of disk space and reduces build-times, when a package is already available.
|
||||
|
||||
Additionally a cache server can be setup and used during pipeline builds to decrease network traffic and build times.
|
||||
Additionally, a cache server can be setup and used during pipeline builds to decrease network traffic and build times.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: "Remix"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend]
|
||||
title: "Remix"
|
||||
ring: adopt
|
||||
quadrant: languages-and-frameworks
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
Updated to "adopt"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: "Semanticore"
|
||||
ring: adopt
|
||||
quadrant: tools
|
||||
tags: [ci/cd, documentation, quality assurance]
|
||||
tags: [ci/cd, documentation, quality assurance]
|
||||
---
|
||||
|
||||
Updated to adopt.
|
||||
|
||||
@@ -1,10 +1,11 @@
|
||||
---
|
||||
title: "SpecFlow"
|
||||
ring: assess
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding, quality assurance]
|
||||
title: "SpecFlow"
|
||||
ring: assess
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding, quality assurance]
|
||||
---
|
||||
|
||||
SpecFlow is a free and open source BDD-framework for .NET
|
||||
[SpecFlow](https://specflow.org) is a free and open source BDD-framework for .NET
|
||||
|
||||
BDD frameworks in general enable teams to better collaborate on test automation by using for instance the Gherkin syntax to make tests readable to everyone. SpecFlow is the most popular BDD framework for .NET projects.
|
||||
BDD frameworks in general enable teams to better collaborate on test automation by using for instance the Gherkin syntax
|
||||
to make tests readable to everyone. SpecFlow is the most popular BDD framework for .NET projects.
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: "Svelte"
|
||||
ring: assess
|
||||
quadrant: "languages-and-frameworks"
|
||||
featured: true
|
||||
tags: [coding, frontend]
|
||||
title: "Svelte"
|
||||
ring: assess
|
||||
quadrant: "languages-and-frameworks"
|
||||
tags: [coding, frontend]
|
||||
---
|
||||
|
||||
[Svelte](https://svelte.dev/) is neither a language nor a framework, but actually a compiler. It compiles HTML templates to specialized code that
|
||||
manipulates the DOM directly, which may reduce the size of transferred files and give better client performance.
|
||||
[Svelte](https://svelte.dev/) is neither a language nor a framework, but actually a compiler. It compiles HTML templates
|
||||
to specialized code that manipulates the DOM directly, which may reduce the size of transferred files and give better
|
||||
client performance.
|
||||
|
||||
It is surprisingly easy to work with, and we currently assess it in an internal project.
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
title: "Turborepo"
|
||||
ring: trial
|
||||
quadrant: "tools"
|
||||
featured: true
|
||||
tags: [build, frontend]
|
||||
title: "Turborepo"
|
||||
ring: trial
|
||||
quadrant: "tools"
|
||||
tags: [build, frontend]
|
||||
---
|
||||
|
||||
[Turborepo](https://turbo.build/repo) is a build system for JavaScript and TypeScript project,
|
||||
|
||||
Reference in New Issue
Block a user