Add mention about Bump.sh API Explorer in relevant pages #327
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for bump-content-hub ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
grossyoan
approved these changes
Jan 31, 2025
ChristopheDujarric
requested changes
Feb 3, 2025
| @@ -67,6 +67,7 @@ There are many tools to help you get the most out of OpenAPI, at every step of t | |||
|
|
|||
| ### Testing | |||
|
|
|||
| * [Bump.sh](https://bump.sh/api-documentation) 💙 | |||
There was a problem hiding this comment.
Suggested change
| * [Bump.sh](https://bump.sh/api-documentation) 💙 |
It's not "testing" in the same sense. Testing, in this paragraph, is about automated/technical tests
Comment on lines
27
to
28
| > Bump.sh now includes its own [API Explorer](https://docs.bump.sh/product-updates/2025/01/09/api-explorer/), allowing you to test your API directly within your documentation. [Give it a try !](https://bump.sh/demo/doc/api-explorer/explorer/operation/operation-adduser) | ||
|
|
There was a problem hiding this comment.
Suggested change
| > Bump.sh now includes its own [API Explorer](https://docs.bump.sh/product-updates/2025/01/09/api-explorer/), allowing you to test your API directly within your documentation. [Give it a try !](https://bump.sh/demo/doc/api-explorer/explorer/operation/operation-adduser) |
Although this can be valuable information for our readers, I would refrain from adding it in this specific text, which focuses on Technical Writers skills rather than tooling.
ChristopheDujarric
approved these changes
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I’ve chosen to announce the availability of the new API Explorer as a callout on the relevant pages, with a link to the PU and a demo doc.
I believe I’ve covered all the relevant pages, but let me know if the wording works for you!