[Extension-docs] New Getting started with Chrome Extensions section

[AmySteam]

trafficstars

Problem

The current Getting Started Chrome Extension tutorial doesn't cover many common use cases for Chrome extension development.

Goal

Add a Getting Started section that helps developers begin their Chrome Extension learning journey.

Articles:

• Two conceptual docs introduce developers to basic extension concepts and the development workflow.
  • Extensions 101
  • Development Basics
• Three beginner extension tutorials that teach common use cases: inject an element on every page, change the aspect of the current page, and a tabs manager.
  • Reading time
  • Focus Mode
  • Tabs Manager

📝 Todos:

• [ ] Add page: Introduction to Getting Started guide
• [ ] Add blog announcement
• [ ] Update Extensions Welcome page.
• [ ] Identify other docs that link to the Getting Started docs.

[netlify[bot]]

✅ Deploy Preview for developer-chrome-com ready!

Name	Link
🔨 Latest commit	ce19ea740276be4128aa7acce9da5f9a8be73561
🔍 Latest deploy log	https://app.netlify.com/sites/developer-chrome-com/deploys/633c57fa73b46900070d6e21
😎 Deploy Preview	https://deploy-preview-3328--developer-chrome-com.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[rachelandrew]

@AmySteam I just had a quick read through these and they are really great. If you'd like a tech writer review, happy to do that, but just wanted to mention how good this is all looking.

[chrome-devrel-review-bot]

Hello! This is an automated review by our custom reviewbot. It updates automatically when code or GitHub comments in this pull request are created or updated.

Requested changes

If there are any common problems with the content files you created or modified, they will be listed here.

site/en/docs/extensions/mv3/getstarted/development-basics/index.md

• This file passed all of our automated Markdown audits.

site/en/docs/extensions/mv3/getstarted/extensions-101/index.md

• This file passed all of our automated Markdown audits.

site/en/docs/extensions/mv3/getstarted/tut-focus-mode/index.md

• This file passed all of our automated Markdown audits.

site/en/docs/extensions/mv3/getstarted/tut-reading-time/index.md

• This file passed all of our automated Markdown audits.

site/en/docs/extensions/mv3/getstarted/tut-tabs-manager/index.md

• This file passed all of our automated Markdown audits.

site/en/docs/extensions/mv3/getstarted/index.md

• Please change your usage of the following words:
  • Avoid please. Affected lines: 67

[AmySteam]

@rachelandrew Thanks for taking the time to look at these! Your initial impression made my day 😄. I would appreciate a tech review. FYI: I will be OOO next week, so you can take your time. Thanks again!! 😸

[AmySteam]

@jpmedley There are a few changes still needed for the tabs-manager tutorial, but the rest of the files are ready for an editorial review. Thanks! 😄

[jpmedley]

It looks like "host_permissions" is still unresolved. Have you made a decision?

[jpmedley]

I've been meaning to ask on the folder structure issue: do we know an engineer with a physical impairment who could just advise us on the best course?

[AmySteam]

@jpmedley In the meantime, I switched the folder structures to images with alt text. But, it's a good idea to seek more guidance.

I'd like to merge this PR early next week, so we can apply any suggestions on a separate PR 👍

[jpmedley]

And I approved it and forgot to assign it back to you . sorry about that.

[jpmedley]

@AmySteam The broken checks appear to be false negatives. What help do you need to get this out?

[AmySteam]

@jpmedley The PR#3717 updates the Chrome Extension Welcome page. I was waiting on a tech review, but since the changes are mostly structural, maybe we can go directly to an editorial review? I would appreciate your help with that.