ampproject / ampproject/amp.dev

Content proposal

Open
#7,102 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
600
Forks
675
PR merge metrics
No merged PRs in 30d

Description

## 📝 Content Proposal

### Synopsis
A clear and concise description of the content you will be contributing.

### Content type

- [ ] Guide
- [ ] Tutorial
- [ ] Example
- [ ] Translation
- [ ] Other (please specify)

### Process
Read the [contributing guide](https://amp.dev/documentation/guides-and-tutorials/contribute/contribute-documentation/?format=websites), then create a copy of [this template](https://docs.google.com/document/d/18i_lbQ-h-auYW2SwbWRuuu2_xhtU5XrjXlcCtj0sNeY/edit?usp=sharing) and fill in the proposal and outline sections. When you’ve finished, add the link to this issue and check the box for step one. A member of the AMP team will assign the ticket to themselves and work as your reviewer through the remaining steps. Thanks for contributing to AMP!

- [ ] 1. Proposal created: ``.
- [ ] 2. Proposal approved.
- [ ] 3. Draft complete.
- [ ] 4. Draft approved.
- [ ] 5. Pull request submitted.
- [ ] 6. Pull request approved!

Contributor guide

Open the contributing guide

Research direction

Start by reading the contributing guide linked in the issue, then copy the provided Google Docs template. Fill in the proposal and outline, add the document link to step one, and wait for AMP team review before proceeding through the remaining checklist.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.