Updates to Extensions section #2034
Conversation
| @@ -6,7 +6,32 @@ weight: 700 | |||
|
|
|||
| # Extensions | |||
There was a problem hiding this comment.
@dgzlopes do you think we should get rid of all of this information?
I know we have other sections that just include the {{< section >}} shortcode, but I do think the information we had on this page was helpful.
There was a problem hiding this comment.
I see you removed a bunch of things we had there originally 👀
It's much better. Still, the use cases are outdated. xk6-kubernetes is not officially maintained. Prometheus RW is now in core, so being an extension is not relevant. The last one about distributed tracing is archived.
There was a problem hiding this comment.
Ok, that's helpful! I removed the use cases section, we do at least list some use cases when talking about the types of extensions in the introduction.
| @@ -1,67 +1,65 @@ | |||
| --- | |||
| title: 'Explore extensions' | |||
| menuTitle: 'Explore extensions' | |||
| description: 'Explore the k6 extension ecosystem to find extensions that meet your requirements.' | |||
| description: 'Explore the k6 extension ecosystem to find extensions that fit your use cases.' | |||
| weight: 01 | |||
| --- | |||
|
|
|||
| # Explore extensions | |||
There was a problem hiding this comment.
@dgzlopes wanted to ask you again here, I saw there were some conversations around how to organize the official/community vs cloud/custom binary extensions.
What do you think if we change the headings on this page to what I did here:
- Official extensions
- Community extensions
- Use extensions
- Automatic extension resolution
- Custom k6 binary
If that doesn't sound good, I can change it back, I just might tweak the headings a little bit.
There was a problem hiding this comment.
This new iteration looks good to me 👍
What?
Updates to the extension section.
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/k6/nextfolder of the documentation.docs/sources/k6/v{most_recent_release}folder of the documentation.Related PR(s)/Issue(s)
#2030