Brett Hayes

The following works. Tested with `[email protected]`. ```jsx // Menu Component import { Link } from 'react-scroll'; Section ``` ```jsx // Section Component import { Element } from 'react-scroll'; ```

A quick fix until this is implemented; if you convert your PR to a draft and then click the "Ready for review" button, it will re-trigger the notification in Slack....

The latter comment was completed in #5494 but we have #483 to check for broken links.

@elzannewentzel I think re-submitting a new `sitemap.xml` to the Google Search Console should fix the first 3 rows listed in that spreadsheet since row 2 and 3 probably won't ever...

I've submitted the newly generated [sitemap.xml](https://search.google.com/search-console/sitemaps/info-drilldown?resource_id=sc-domain:sourcegraph.com&sitemap=https:%2F%2Fabout.sourcegraph.com%2Fsitemap.xml) for About in GSC under the dot com property. I also submitted the [handbook sitemap](https://search.google.com/search-console/sitemaps/info-drilldown?resource_id=sc-domain:sourcegraph.com&sitemap=https:%2F%2Fhandbook.sourcegraph.com%2Fsitemap.xml) as well. So that should fix all 4 rows...

The Video component updates were updated in #5493. Other styling initiatives will be tackled in #5381.

Here's what I'm thinking to clean up and standardize our interfaces with file organization and naming conventions: ## Rules of thumb/style guide: 1. If one or more interfaces are needed...

@zlonko I'm leaning more towards one for much more robust search and batch changes. `{YourInterfaceName}Props`

@st0nebraker just following up to define how we can tackle this progressively going forward by creating new logic and updating logic as we come across it. Let's use the following...

You should be all set now @nickmyyz. Let me know if that works for you. 🙂 1. We updated our tsconfig since this PR was created so I merged main...