GoogleChrome/developer.chrome.com

content: TODO

ender700 opened this issue · 0 comments

  • Use this template to propose new content.
  • Delete any fields that aren't relevant to your issue.
  • Update the title of this issue with a brief summary of the work to be done.

Workflow for Googlers

Fill out the content proposal form: https://docs.google.com/forms/d/e/1FAIpQLSc65CDClpUu7R2ECacLz3B1a6hOCWdFAk2vkWXIbZjzNSXq_Q/viewform?resourcekey=0-t3rJNkt5V2-iE2N42KhrhQ

Don't create an issue here on GitHub! Your GitHub issue will be closed
immediately and you'll be asked to fill out the form instead.

Content proposal form for contributors who don't have access to Googlers

Fill out this section ONLY if you want to contribute new content to developer.chrome.com but don't have access to
Googlers.

Provide a brief title for your content proposal

Provide a brief summary of your content proposal

Please explain how this content will help me be a better web developer.

What content already exists on this topic?

Provide a list of URLs.

Who will be authoring the content?

Provide a list of GitHub usernames.

Are there any stakeholders who should be informed when this content changes?

Provide a list of GitHub usernames.

What area is your content related to?

Choose from one of the following: Accessibility, PWAs/Capabilities, Frontend, Holotypes, Performance, Privacy/Security, Other

What kind of content are you creating?

Choose from one of the following: Blog Post, Case Study, Codelab, Guide, Other