| body{ | |
| font-weight: bold; | |
| font-size: 50px; | |
| text-transform: uppercase; | |
| } | |
| body code{ | |
| background-color:#d2f2f2; | |
| padding: 0 .5rem; | |
| display: inline-block; |
| /** | |
| * Анимация по hover (как это делать не нужно) | |
| */ | |
| div { | |
| width: 9em; | |
| padding: .6em 1em; | |
| margin: 2em auto; | |
| background: yellowgreen; | |
| } |
| /** | |
| * Анимация по hover (правильная) | |
| */ | |
| div { | |
| width: 9em; | |
| padding: .6em 1em; | |
| margin: 2em auto; | |
| background: yellowgreen; | |
| animation: spin 1s linear infinite; |
The role of Facilitator is fundamental for almost every meeting. The Facilitator ensures that the whole group is empowered to make decisions and that every individual has their voice heard.
During a retrospective, the Facilitator role is crucial. In a retrospective, it is ideal that everyone has at least some degree of participation, and it is the Facilitator that helps the participants with that.
Before we begin talking about the trade-offs, let's look at the desired state, why someone should use Web Components and what benefits it provides. This standard allows you to create framework-independent UI components. Instead of re-inventing the same concept of UI component for every framework, there could be a universal solution using Web Components standard. They will also be more simple and lightweight, as the API is already built into browsers and you do not need to load additional runtime to your web page.
Web Components are defined as custom HTML elements where you can attach your custom behavior. You do not need to learn additional proprietary framework conventions, as you can think about using Web Component same way as you would use <button> or <input>.
Now let's check how these expectations match with the real state.
