Restructure content presented under API Policy related documentation
Open
Nobody has claimed this yet.
API-M 4.2.0
API-M-4.1.0
API-M-4.3.0
API-M-4.4.0
API-M-Master
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
We should consider on how we can structure this API Policy content better as we no longer have the CC policies mentioned in our docspace. Also, Revoke One Time Tokens Policy is out of place as shown in the below screenshot.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the API Policy documentation referenced in the issue and compare its current organization with the supplied screenshot. Review the obsolete CC policy references and the placement of Revoke One Time Tokens Policy. Done means the content has a clear, consistent structure and no outdated policy references remain.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100