Melanie Sumner MelSumner

Just some Fonts

Just some fonts/font-pairings I enjoy.

Working on ways to better display "our staff" or "staff directory" pages....than a table. Because Seriously. Tables. No.

Shuffle between page images with animated states. From Web Designer Magazine, Issue 223.

Awesome things you can do with bootstrap and angularJS.

Ember has been around since 2011. It's also not the product it was in 2011, and has adapted/evolved into an experienced, dependable ecosystem.
"Safety of the Herd" (article) illustrates that we get to solve more interesting problems when the entire community adheres to a shared set of standards.
"How to learn EmberJS in a hurry" (article) illustrates that the Ember learning curve may not be as steep as you think.
Ember's testing story is superb, and the core team demonstrated the wisdom that comes only through experience, by making it a core feature that is equally as important as the framework itself.
Accessibility- the ember-a11y community and growing collection of addons demonstrates the commitment to the idea that people of all abilities should be able to use the web

	import Ember from 'ember';

	const LANDMARK_NAVIGATION_ROLE = {
	_default: 'region',
	header: 'banner',
	nav: 'navigation',
	aside: 'complementary',
	main: 'main',
	footer: 'contentinfo',
	form: 'form',

	Acceptance criteria:
	* must use semantic HTML
	* must have the correct ARIA roles (when necessary)
	* must read out in a logical manner when assistive technology (AT) is used
	* must use Ember correctly

	Challenging UI Components:
	[ ] radio button label contains a dropdown with options in it. Speech viewer should read entire thing correctly.
	[x] a dropdown menu where the last X number of items are not interactive (menuitems), but are simply additional text items (i.e., "Last Login" type of info)
	[ ] a data table that keeps semantic html

	Recommended (S)CSS guidelines - this is how I have successfully managed stylesheets in my projects.
	P.S. If your css follows these guidelines then I can help you much faster and ship lots more code...

	# normalizer over reset
	# don't use IDs
	# lowercase class names
	# put classes in alphabetical order (actually alpha-order as many things possible)
	# color variable names: color first, then shade
	-- example: $blue, $blue-light, $blue-dark. If you really need to, you can do $blue-lighter $blue-darker.
	# don't reassign color variables. take the time to learn them. it will become second nature. promise.

	1. if you are not yet familiar with the CSS structure, please do one of two things:
	--put the CSS you think you need into the wip.scss file and tag @MelSumner in your commit (I'll put it in the correct place)
	--get to know the awesome organized awesomeness of the CSS. It might feel tight at first, like a new pair of shoes, but they will be awesome shoes after a while.

	2. Writing CSS Rules because I love you but I've chosen process.
	# keep specificity low. If you're getting really specific, I'm so sorry to have to be the one to tell you this, but you're wrong.
	# don't use IDs
	# lowercase class names, please.
	# put classes in alphabetical order if you can.
	# put the properties in alpha-order. It's usually as easy as highlighting the properties and hitting F9.