Merge branch 'barrierefreiheit' into 'main'

Edit .glossary.yaml by adding more abbeviations

See merge request open-code/badgebackend/badge-api-documentation!7

.glossary.yaml

@@ -22,5 +22,19 @@ ID: Short for "identifier" – a unique value or token used to distinguish an en
 SVG: Scalable Vector Graphics – an XML-based vector image format for two-dimensional graphics, supporting interactivity and animation.
 ZenDiS: The Zentrum für Digitale Souveränität der Öffentlichen Verwaltung (ZenDiS - Centre for Digital Souvereignity in Public Administration) has become responsible for openCode and is continuously developing the platform.
 BITV: Short for "Barrierefreie Informationstechnik-Verordnung 2.0" – the German regulation that sets mandatory accessibility standards for public websites and mobile applications, ensuring digital inclusion for users with disabilities.
+yaml: is a human-readable data serialization language. It is commonly used for configuration files and in applications where data is being stored or transmitted
+YAML: is a human-readable data serialization language. It is commonly used for configuration files and in applications where data is being stored or transmitted
+git: is a distributed version control system that tracks versions of files. It is often used to control source code by programmers who are developing software collaboratively.
+e.g.: example given
+json: Short for "JavaScript Object Notation" – a lightweight, human-readable data format used for structured data interchange.
+regex: A regular expression (shortened as regex or regexp), sometimes referred to as rational expression,is a sequence of characters that specifies a match pattern in text. Usually such patterns are used by string-searching algorithms for "find" or "find and replace" operations on strings.
+CVE: The Common Vulnerabilities and Exposures (CVE) system provides a reference method for publicly known information-security vulnerabilities and exposures. 
+container registry: Eine Container Registry ist ein Repository oder eine Sammlung von Repositories, in der Container Images gespeichert werden und auf diese Images zugegriffen werden kann. Container Registries können die containerbasierte Anwendungsentwicklung unterstützen, was häufig im Rahmen von DevOps-Prozessen geschieht. Container Registries können eine direkte Verbindung zu Container-Orchestrierungsplattformen wie Docker und Kubernetes herstellen
+pipeline: a pipeline refers to a series of automated steps that optimize the software delivery process. These steps include building, testing, and deploying code, aiming to improve the app development process through monitoring and automation. This is particularly helpful during integration and continuous testing phases, which can be challenging and time-consuming without automation. Pipelines can prevent errors that might occur due to manual processes, enable quick product iterations, and provide consistent feedback throughout the development process
+bug: a bug refers to an error, flaw, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. Bugs can range from minor issues, such as a user interface glitch, to major problems that can cause the program to crash or compromise security.
+commit: In the context of software development, a commit refers to the act of saving changes to a version control system, such as Git. When you commit, you are recording the changes you've made to the codebase, along with a message that describes what was changed. This creates a snapshot of the project at that point in time, allowing you to track the history of changes, revert to previous versions if needed, and collaborate with other developers.
+tags: tags are references to specific points in the repository's history. They are often used to mark important milestones, such as releases or significant changes. Here are some key points about tags
+tag: Tags are often used to mark the release versions of software, can help in branching and merging by providing clear reference points, can mark significant commits that are not necessarily releases, such as the start of a new feature or a major refactor.
+release: A release in the context of Git is a formal version of your software that is ready for distribution or deployment. It is typically marked with a tag, and the process often involves creating a release branch, merging changes back to the main branch, and using CI/CD pipelines to build and deploy the release. This ensures that the release is stable, well-tested, and can be deployed reliably.