IGNORE prefers-color-scheme article for web.dev

.eleventy.js

@@ -35,8 +35,10 @@ const Breadcrumbs = require(`./${componentsDir}/Breadcrumbs`);
 const CodelabsCallout = require(`./${componentsDir}/CodelabsCallout`);
 const Compare = require(`./${componentsDir}/Compare`);
 const Hero = require(`./${componentsDir}/Hero`);
+const Instruction = require(`./${componentsDir}/Instruction`);
 const PathCard = require(`./${componentsDir}/PathCard`);
 const PostCard = require(`./${componentsDir}/PostCard`);
+const YouTube = require(`./${componentsDir}/YouTube`);
 
 const collectionsDir = 'src/site/_collections';
 const postDescending = require(`./${collectionsDir}/post-descending`);
@@ -121,10 +123,12 @@ module.exports = function(config) {
   config.addShortcode('CodelabsCallout', CodelabsCallout);
   config.addPairedShortcode('Compare', Compare);
   config.addShortcode('Hero', Hero);
+  config.addShortcode('Instruction', Instruction);
   config.addShortcode('PathCard', PathCard);
   config.addShortcode('PostCard', PostCard);
   config.addShortcode('ShareAction', ShareAction);
   config.addShortcode('SubscribeAction', SubscribeAction);
+  config.addShortcode('YouTube', YouTube);
 
   // https://www.11ty.io/docs/config/#configuration-options
   return {

CODEOWNERS → .github/CODEOWNERS

@@ -6,4 +6,6 @@
 * @robdodson
 
 # Guide collections
-/content/ @robdodson @Meggin
+content/ @robdodson @Meggin @mfriesenhahn
+
+content/en/react/ @housseindjirdeh @robdodson

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Found a bug? Let us know!
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.

.github/ISSUE_TEMPLATE/content_request.md

@@ -0,0 +1,18 @@
+---
+name: Request an article
+about: Suggest an article for the site.
+title: ''
+labels: content request
+assignees: ''
+
+---
+
+**Describe the article you'd like to see**
+What topics should it cover? Who is the intended audience?
+
+**Publish date**
+When would you like to see this article go live? Is this a hard deadline?
+
+---
+
+If you plan to write the article yourself be sure to read through [our wiki](https://github.com/googlechrome/web.dev/wiki) which explains how to add a new post to the site.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project.
+title: ''
+labels: feature request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -5,34 +5,3 @@ Changes proposed in this pull request:
 - 
 - 
 - 
-
----
-
-If this PR adds **new content** please fill out the form below.
-If this PR changes existing content you can delete the form.
-
----
-
-👋 Thanks for submitting this PR! Please take a moment to let us know what's been added.
-
-To mark a box as done, add an x like so:
-- [x] This todo is complete!
-
-This pull request adds a **new**:
-- [ ] Guide(s) 📘
-- [ ] Codelab(s) 🔬
-
-Have you read the wiki on writing [a guide](https://github.com/GoogleChrome/web.dev/wiki/How-to-write-a-post) or [a codelab](https://github.com/GoogleChrome/web.dev/wiki/How-to-write-a-codelab)?
-- [ ] Done! 🍰
-
-Does your content tell a user how to fix a Lighthouse audit?
-Have you added [the Lighthouse audit ID to your YAML](https://github.com/GoogleChrome/web.dev/wiki/How-to-write-a-guide#lighthouse-audits)?
-- [ ] My changes do not mention Lighthouse audits. 🙅‍♂️
-- [ ] I have added the Lighthouse audit IDs to my content. 👍
-
-Does your content reference any Glitch projects?
-Have you read the wiki on [working with Glitch](https://github.com/GoogleChrome/web.dev/wiki/Working-with-Glitch)?
-Have you added the Glitch project to [our team page](https://glitch.com/@webdev)?
-- [ ] My changes do not contain any Glitches. 🙅‍♂️
-- [ ] I have read the wiki on working with Glitch. 🍰
-- [ ] I have added my Glitches to the team page. 👏

README.md

@@ -8,7 +8,7 @@ help them apply what they've learned to any site they work on, be it personal or
 business.
 
 Note: this repo contains the written content for web.dev. The client-side JS and
-server are not yet open source.
+server are not yet open source but we hope to share them soon! 🙇‍♂️
 
 ## Authoring content