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

DOCS-679 - Kanso / New UI default #5061

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

DOCS-679 - Kanso / New UI default #5061

wants to merge 3 commits into from

Conversation

kimsauce
Copy link
Collaborator

@kimsauce kimsauce commented Feb 12, 2025

Purpose of this pull request

Kanso - New UI becomes the default UI at sign-in (instead of Classic UI).

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-679

@cla-bot cla-bot bot added the cla-signed Contributor approved, listed in .clabot file label Feb 12, 2025
@kimsauce kimsauce self-assigned this Feb 12, 2025
@kimsauce kimsauce requested a review from kevin-sumo February 12, 2025 08:27
@kimsauce kimsauce added the do-not-merge Pull requests that should not be merged label Feb 12, 2025
@kimsauce kimsauce changed the title Kanso - New UI default DOCS-678 - Kanso / New UI default Feb 12, 2025
@kimsauce kimsauce changed the title DOCS-678 - Kanso / New UI default DOCS-679 - Kanso / New UI default Feb 12, 2025
Copy link
Collaborator

@jpipkin1 jpipkin1 left a comment

Choose a reason for hiding this comment

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

Looks great, @kimsauce!


## Why this change and what’s improved

The Classic UI will be permanently retired in spring 2025 and will no longer available. For the latest features, performance improvements, and future innovations, switch to the New UI as soon as possible, which offers:
Copy link

Choose a reason for hiding this comment

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

in spring 2025

I don't think we should say this externally yet, the date is contingent on some infra/test coverage and also addressing critical feedback (which we are still continuing to collect). If we do want to communicate something I would say it will be permanently retired this year 2025. The target of 3-6 months from now is flexible (and some orgs may still request access to the old UI for longer). cc: @kevin-sumo

* **New orgs use only the new UI**. If your org was created after this change, the Classic UI will not be available.
* **MSSP exception**. If your org was created through a parent org, you can still switch to the Classic UI.

## Why this change and what’s improved
Copy link

Choose a reason for hiding this comment

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

I would suggest restructuring these sections and separating them. Basically:

Why this change

What is changing

How has it improved since initial GA (instead of "What's improved")

Reasoning for this is Bento has many of the features we are saying are improvements and that may be interpreted as it being an improvement over Bento vs improvements since we initially released it (last year).

:::warning Transition to the New UI
The Classic UI will be retired in early 2025. To ensure you have access to the latest features and updates, we recommend transitioning to the [Sumo Logic New UI](/docs/get-started/sumo-logic-ui) at your earliest convenience.
:::warning Classic UI retirement notice
The Classic UI will be retired in spring 2025 and will no longer receive updates. For the latest features, performance improvements, and future innovations, switch to the [New UI](/docs/get-started/sumo-logic-ui) as soon as possible.
Copy link

Choose a reason for hiding this comment

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

in spring 2025

Same comment as above, I would like to be a little more vague as to the date and possibly add a note that we will start communicating the date within 3 months of the target. I would like to have a little more confidence in the date before we start exposing it externally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants