YAML

Automating your workflow can be achieved by using pipelines as they are the heart of the CI process in Microtica. The build process of every component and microservices, whether it’s triggered manually or automatically, is done in a pipeline. The build process is defined by a single source of truth, a microtica.yaml file in the root folder of the repository. With user customizability as a key feature, every user is able to define how their build process is done and what commands are ran by changing the microtica.yaml file.

XAML is a declarative markup language. As applied to the .NET Core programming model, XAML simplifies creating a UI for a .NET Core app. You can create visible UI elements in the declarative XAML markup, and then separate the UI definition from the run-time logic by using code-behind files that are joined to the markup through partial class definitions. XAML directly represents the instantiation of objects in a specific set of backing types defined in assemblies. This is unlike most other markup languages, which are typically an interpreted language without such a direct tie to a backing type system. XAML enables a workflow where separate parties can work on the UI and the logic of an app, using potentially different tools. When represented as text, XAML files are XML files that generally have the .xaml extension. The files can be encoded by any XML encoding, but encoding as UTF-8 is typical.