added more sections

Author: MelSumner

Diff for: README.md

@@ -5,10 +5,12 @@ A Handbook of notes for the Ember Learning Core Team. This repo helps us track t
 
 ## Contents
 
-- [infrastructure](01_infrastructure.md)
-- [heroku & fastly setup](02_heroku_fastly_setup.md)
-- [website- sitemap](03_website_sitemap.md)
-- [website- accessibility](04_website_accessibility.md)
+- [infrastructure](infrastructure.md)
+- [heroku & fastly setup](infra_heroku_fastly_setup.md)
+- [website- sitemap](website_sitemap.md)
+- [website- accessibility](website_accessibility.md)
+- [website- seo](website_seo.md)
+- [website- design](website_design.md)
 
 ## Contributing
 

Diff for: 02_heroku_fastly_setup.md renamed to infra_heroku_fastly_setup.md

@@ -0,0 +1,9 @@
+# Website- Design
+
+## Styling and shared components
+
+- Styling and shared components are managed through the [ember-styleguide](https://github.com/ember-learn/ember-styleguide).
+- Any proposed style must follow the branding guidelines (available on emberjs.com).
+- Upstream changes are preferred to overrides.
+- We will use themes to give the flexibility to implement (and develop) new themes.
+- All of the code should be kept as simple as possible, to make it easy to contribute. Complexity on these sorts of sites will end up being a wall between contributors and code; community members shouldn’t have to learn new tools just to contribute.

Diff for: 01_infrastructure.md renamed to infrastructure.md

@@ -0,0 +1,17 @@
+# SEO
+
+We will employ standard SEO techniques (as standard as we can, since they seem to change over time)
+
+- We will use standard “semantic web” and Accessibility - these also support SEO. (Use of <h1> tags for example)
+- As most SEO things are rule of thumb we need to be constantly tracking our ranking and running “experiments” to improve our rankings for specific keywords
+  [ ] create to-do list for how to track our ranking, to include method for sending regular reports to a place where they can be reviewed by the learning team
+  [ ] plan running experiments to improve rankings for specific keywords
+- [ ] decide: what specific keywords we want to track
+- [ ] decide: what tool we are using to track ranking
+- sub-domains are treated “mostly the same” as sub folders for SEO purposes
+[ ] track and improve LH scores for all Ember sites: Google has mentioned that they take Lighthouse scores into account, so while this is relevant to every section in this document it should be considered particularly important to track and improve Lighthouse scores for all Ember sites 
+[ ] decide: what kind of metrics do we want to gather, and how often?
+
+## Learn More
+
+- A lot of SEO techniques are more like rules of thumb than scientific to-do lists, if anyone is interested in learning some of the best practices I would recommend https://moz.com/ which has a lot of free content