Featured image of post SPAC: Web APIs for Page Transitions & Persistence

SPAC: Web APIs for Page Transitions & Persistence

_SPAC is a custom JavaScript framework for client-side, single-page web applications. It stands for "Stateful Pages, Actions and Components". Its design goal is to provide robust and simple entities that help you to structure apps. Pages and components provide the HTML, JavaScript functions and UI interactions. Actions govern external API calls. You define these entities in plain JavaScript, load up the central controller, and your app is ready to be served. Read the development journey of SPAC in my series: <https://admantium.com/category/spac-framework/>._

Featured image of post SPAC: Controller Self-Initialization & Object API

SPAC: Controller Self-Initialization & Object API

_SPAC is a custom JavaScript framework for client-side, single-page web applications. It stands for "Stateful Pages, Actions and Components". Its design goal is to provide robust and simple entities that help you to structure apps. Pages and components provide the HTML, JavaScript functions and UI interactions. Actions govern external API calls. You define these entities in plain JavaScript, load up the central controller, and your app is ready to be served. Read the development journey of SPAC in my series: <https://admantium.com/category/spac-framework/>._

Featured image of post SPAC: Controller Implementation

SPAC: Controller Implementation

ApiBlaze is a tool to explore API specifications: Search for a keyword, filter for objects, properties, or endpoints, and immediately see descriptions and code examples. ApiBlaze helps you to answer a specific question about an API lightning fast. You can try it here: [apblaze.admantium.com](https://apiblaze.admantium.com).

Featured image of post ApiBlaze: Development Phases

ApiBlaze: Development Phases

_ApiBlaze is a tool to explore API specifications: Search for a keyword, filter for objects, properties, or endpoints, and immediately see descriptions and code examples. ApiBlaze helps you to answer a specific question about an API lightning fast._

Featured image of post ApiBlaze: A new Developer Journey

ApiBlaze: A new Developer Journey

ApiBlaze is my new project, and this is the first post in a developer journal series - a set of related posts that cover individual aspects of the design, implementation and technologies. In this very first article, I explain the motivation, the key features, technologies and requirements to start the realization of ApiBlaze.

Featured image of post Learning JavaScript: Project Recap

Learning JavaScript: Project Recap

JavaScript is a fascinating and well-used language. From server-side NodeJS applications to frontends with PlainJS or frameworks like React, it powers many services. Since 2019 I have been working on several projects to learn and explore JavaScript. This blog post is a short recap of those projects, and then gives an outlook to my newest endeavor.

Featured image of post Ansible: Idempotent Playbooks

Ansible: Idempotent Playbooks

Effective Ansible playbooks are idempotent: They change a system to the very same state independent of the systems current state. To achieve this, a clearly structured directory layout and custom uninstaller tasks are helpful. Learn more in my new article: https://admantium.com/blog/a05_idempotent_playbooks

Featured image of post Ansible: Checking and Controlling Task Execution, Orchestration and Scope

Ansible: Checking and Controlling Task Execution, Orchestration and Scope

Running Ansible professionally leads to the one and only `site.yml` file, defining which roles and tasks should be executed on each host. But now, how can you only run specific tasks, targeting specific hosts? Learn about cmdline flags in my new article: https://admantium.com/blog/a04_controlling_task_execution

Featured image of post Ansible: Influencing Action Execution with Conditions and Branches

Ansible: Influencing Action Execution with Conditions and Branches

When you execute an Ansible playbook, all actions are run top-down, in the order they are written. There are cases when you need more control, such as defining when to execute an action, defining when to stop an action, branching the control flow, and controlling action results.