Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: update first step of creation screen #10203

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anthonyjgatti
Copy link
Contributor

@anthonyjgatti anthonyjgatti commented Dec 19, 2024

Issue

https://gravitee.atlassian.net/browse/APIM-8045

Description

Goal is to update getting started screen to make things clearer for v2 vs. v4.


📚  View the storybook of this branch here

name: 'Classic (v2) and New (v4) APIs compared',
information: {
description:
'Gravitee v4 APIs contain most of the same capabilities as v2 APIs, including analytics, logs, failover, and health check. They also support some features not available in v2 APIs, such as protocol mediation, shared policy groups, and native Kafka support. Some functionality is not yet included, however, including alerts, tenants, and some analytics capabilities.'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'Gravitee v4 APIs contain most of the same capabilities as v2 APIs, including analytics, logs, failover, and health check. They also support some features not available in v2 APIs, such as protocol mediation, shared policy groups, and native Kafka support. Some functionality is not yet included, however, including alerts, tenants, and some analytics capabilities.'
'Gravitee v4 APIs contain most of the same capabilities as v2 APIs, including analytics, logs, failover, and health check. They also support some features not available in v2 APIs, such as protocol mediation, shared policy groups, and native Kafka support. Some functionalities are not yet included, however, including alerts, tenants, and some analytics capabilities.'

Copy link
Contributor

@jourdiw jourdiw Dec 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use lowercase v4 / v2 or uppercase V4 / V2 ?
We don't necessarily have a hard and fast rule, but in the API List we show it capitalized (V4) 🤷‍♀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants