66 lines
2.1 KiB

layout: default
title: Technology choices
parent: Architecture
nav_order: 2
permalink: taskweave/project/architecture/technology
# Taskweave Technology Choices
{: .no_toc }
<details markdown="block">
Table of contents
{: .text-delta }
## Introduction
{: .todo}
> Turn explanation into a process recipe.
{: .hint}
> Detailed information about [Using Technology Radars](#) can be found in our process recipe.
This page keeps track of major decisions that relate to Taskweave technology stack. Here we explore libraries and frameworks that are candidates to adopt in support of various architecture concepts and requirements. Decisions are ordered in reverse chronological order (Newest-first) and have states. They represent a [Technology Radar]( It has one additional 'Open' state, meaning that an investigation, called a Spike, is planned.:
<div markdown="1">
{: .label .label-green }
{: .label .label-blue }
{: .label .label-yellow }
{: .label .label-red }
{: .label .label-grey }
## Decision Log
### Adopt Elixir PETAL technology stack
{: .label .label-green }
The [PETAL]( stack is a popular combination of frameworks and libraries that have proven to be very powerful and flexible. It consists of:
- [**P**hoenix]( Leading web framework for Elixir.
- [**E**lixir]( Elixir server-side rendering code.
- [**T**ailwind]( CSS framework to mark up HTML with semantic classes.
- [**A**lpine]( Minimal framework for composing JS behaviours in markup.
- [**L**iveview]( Real-time UX with server-rendered HTML.
Elixir and Phoenix Liveview were already part of the stack. Tailwind was a great experience in migration from Bootstrap for []( and is intuitive to use for non-CSS experts.