// users/edit/index.hbs
{{filter-list
items=model
filterBy="path.value"
labelBy="path.value"
highlight=true
order="ASC"}}[![Latest NPM release][npm-badge]][npm-badge-url]
[![TravisCI Build Status][travis-badge-url]][travis-project-url]
[![CircleCI Build Status][circle-badge]][circle-badge-url]
[![Test Coverage][coveralls-badge]][coveralls-badge-url]
[![Code Climate][codeclimate-badge]][codeclimate-badge-url]
[![Ember Observer Score][ember-observer-badge]][ember-observer-badge-url]
[![License][license-badge]][license-badge-url]
[![Dependencies][dependencies-badge]][dependencies-badge-url]
[![Dev Dependencies][devDependencies-badge]][devDependencies-badge-url]
- Hawks vs. Falcons
- Observability vs. Metrics (Cindy Sridharan)
- Events vs. Structured Logs (Ben Hartshorne, Honeycomb.io)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - webpack.config.js | |
| - postcss.config.js | |
| - config.js | |
| - addons.js |
Making the web accessible is important. We have ethical and, in some cases, legal obligations to ensuring access to all of users.
Luckily for us, it's easy to make an accessible Ember Component.
To understand the accessibility story around Ember Components, we have to start by talking about Web Components. Ember Components are designed to be interoperable with the final Web Components API.
A git choose-your-own-adventure!
This document is an attempt to be a fairly comprehensive guide to recovering from what you did not mean to do when using git. It isn't that git is so complicated that you need a large document to take care or your particular problem, it is more that the set of things that you might have done is so large that different techniques are needed depending on exactly what you have done and what you want to have happen.
OlderNewer