imjayanthka

Frontend Masters: AWS for Frontend Engineers

You should have the following completed on your computer before the workshop:

• Install the AWS CLI.
• Have Node.js installed on your system. (Recommended: Use nvm.)
  • Install yarn with brew install yarn.
• Create an AWS account. (This will require a valid credit card.)
• Create a Travis CI account. (This should be as simple as logging in via GitHub).

imjayanthka

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job

imjayanthka

Keybase proof

I hereby claim:

• I am imjayanthka on github.
• I am imjayanthka (https://keybase.io/imjayanthka) on keybase.
• I have a public key ASD660FBatmuIFbvWM_FxmSginzeIIr5ltAcTfaYjiCbMgo

To claim this, I am signing this object: