ampproject / ampproject/amp.dev
Content proposal
- 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
Research direction
Read the linked contributing guide, then copy the Google Docs template and complete its proposal and outline sections. Add the proposal link to this issue and check step 1; completion is indicated by the proposal being created and linked.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100