Doc Feedback:
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Location : https://apim.docs.wso2.com/en/latest/get-started/apim-architecture/
Do we promote Integration studio at the moment. We use Visual studio code plugins for MI and Ballerina integrator.
The term Integration studio might confuse the user.
Regards,
Buddhi
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 with the architecture page at https://apim.docs.wso2.com/en/latest/get-started/apim-architecture/. Verify whether the page should still mention Integration Studio alongside the Visual Studio Code plugins for MI and Ballerina integrator, then update the terminology once the intended current tooling is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100