Brian Ng

@ylemkimon let's update this section to be more explicit: > Example environments: chrome, opera, edge, firefox, safari, ie, ios, android, node, electron. https://github.com/babel/website/blob/master/docs/preset-env.md#targets

@mi-yu only 7.x, and yeah, augmenting https://babeljs.io/docs/en/babel-preset-env#modules with explaining `false`, a specific module type, and `auto` is what we need!

Nice work! I feel like the notification should stand out enough to draw attention, but not be distracting. Maybe black (fits color scheme and contrasts with the yellow header)? 

@gyujincho just took at look at this in IE11... I think we can avoid transpiling, as the only thing that seems to be breaking is: ```js document.querySelectorAll(codeBlockSelector).forEach(...) ``` We can...

> Also it should say somewhere there is nothing magic, Babel does not analyse the code to determine the needed polyfills WRT to the 7 docs, this is not true...

> Clearly state that babel-preset-env is not enough alone, you also need babel-polyfill (or manually include the polyfills you want) I've been working on a preset-env docs overhaul that's long...

Still need to resolve the links in CONTRIBUTING.md that are relative to the repo (vs website). Also, couple of follow up beginner-friendly improvements: - Limit the number of issues? -...

Just so I (and other team members) don't forget, this is applicable if/when https://github.com/babel/babel/pull/9202 lands.

@hpierce1102 yeah, the website is currently using: ``` {% if page.url contains item.url%} ``` to highlight the current section and anything underneath it. Since we're treating `contributing` as a top...

Aligning both the issue number boxes and the edge of the text helps scan-/read-ability: