"create-and-publish-a-graphql-api" doc needs to mention about deployments
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
As it is no longer sufficient to just chaneg tehe lifecyle of the api to "publish", we need to add necessary steps mentioning deployment revisions and add screenshots.
https://apim.docs.wso2.com/en/latest/learn/tutorials/create-and-publish-a-graphql-api/#create-and-publish-a-graphql-api
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
Open the linked create-and-publish-a-graphql-api tutorial and locate its source in the docs repository. Read the existing publishing steps first, then document deployment revisions and add the requested screenshots. Done means the tutorial explains the deployment steps needed after changing the API lifecycle to publish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100