Thomas Gohard thomasgohard

Amazon Alexa development setup for NodeJS

To develop for Amazon Alexa in NodeJS, you will need the following installed on your computer:

NodeJS v8.10 or greater (to match AWS Lambda NodeJS version)
Alexa Skill Kit Command Line Interface
Text editor (e.g., Visual Studio Code)
Git

You will also need the following accounts:

Amazon Alexa account

Overview
- Where things are
- How to navigate the GitHub interface
- The files view vs. the Web view
Issues
- How to submit an Issue
  - On the GitHub interface
  - Via the Web view
- How to participate on an Issue
Filters

Install Ubuntu.
Install Ruby (sudo apt-get install ruby2.0 ruby2.0-dev).
Install github-pages gem (sudo gem install github-pages).

== Resources ==

=== Performance ===

[http://bit.ly/fluent-perf Web performance crash course]
[http://www.youtube.com/watch?v=Il4swGfTOSM Breaking the 1000ms Time to Glass Mobile Barrier]
[http://www.smashingmagazine.com/2013/06/10/pinterest-paint-performance-case-study/ Gone In 60 Frames Per Second: A Pinterest Paint Performance Case Study]
[http://bit.ly/mobilecrp Optimizing the Critical Rending Path - Velocity SC 2013]
[http://dev.opera.com/articles/view/better-performance-with-requestanimationframe/ Better performance with requestAnimationFrame]
[http://www.lukew.com/ff/entry.asp?1793 Smashing Conf: 60 Frames Per Second]

Details/summary

Problem:

The height of a details/summary element pair is equal to the height of the summary element only when the details element is collapsed.
- The details/summary element must be expanded before its height can be calculated.
Setting an equal height on a collapsed element makes it take up the space it would take up while expanded even though it is collapsed.
- The equal height should only apply when at least one more details/summary element pair is expanded on the same baseline.

Temporarily expanding a detail/summary element pair:

elm.setAttribute("open", "open")

Creating content that works on any device

The trick to creating content that works on any device is simple: Create your content for the most restrictive contexts of use first; then enhance your content based on the capabilities of the device used to read it.

This ensures not only that your content can be read on any device, but also that the reading experience is optimised for the device used to read it.

How do you do that?

Focus on your user's needs

Post-installation set-up for Ubuntu

Get the eCryptfs mount passphrase for the home folder

ecryptfs-unwrap-passphrase

	language: ruby

	branches:
	only:
	- master

	script:
	- "bundle exec jekyll build"
	- ./build.sh

	sudo add-apt-repository ppa:chris-lea/node.js
	sudo apt-get update
	sudo apt-get install nodejs
	sudo npm install -g grunt-cli
	sudo npm install -g bower

	# Setup a development environment for AEM using Brackets

	1. Install Brackets.
	2. Install the AEM and Brackets-git extensions.