Skip to content

Restructure Search UI landing page #1628

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

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

Conversation

charlotte-hoblik
Copy link
Contributor

@charlotte-hoblik charlotte-hoblik commented Jun 6, 2025

Preview

This PR restructures the Search UI Documentation landing page to improve clarity, navigability, and alignment with documentation best practices.

This restructure is a second PR toward eliminating duplication between the two main Search UI documentation pages:

https://www.elastic.co/docs/reference/search-ui
https://www.elastic.co/docs/solutions/search/site-or-app/search-ui

Also:

  • Added information on Serverless being compatible with Search UI but not with CORS

Connected to

@charlotte-hoblik charlotte-hoblik self-assigned this Jun 6, 2025
@charlotte-hoblik charlotte-hoblik requested a review from a team as a code owner June 6, 2025 13:01
@charlotte-hoblik charlotte-hoblik added the documentation Improvements or additions to documentation label Jun 6, 2025
Copy link
Contributor

@leemthompo leemthompo left a comment

Choose a reason for hiding this comment

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

TY!

@@ -34,6 +34,7 @@ The information below reflects our strategic goals, plans and objectives and inc
| **User management** | Elastic Cloud-managed and deployment-local users | Elastic Cloud-managed users only. Serverless users are managed at the organization level with SAML authentication support. |
| **Backups** | User-managed with Snapshot & Restore | Automatically backed up by Elastic |
| **Solutions** | Full {{stack}} per deployment | Single solution per project |
| **CORS** | Supported | Not available. Use a backend proxy to enable integrations. |
Copy link
Collaborator

@shainaraskas shainaraskas Jun 11, 2025

Choose a reason for hiding this comment

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

do we have any docs that we can link to that can help people out with this? why is this specifically important for integrations? IMO the implications are not completely clear

Suggested change
| **CORS** | Supported | Not available. Use a backend proxy to enable integrations. |
| **Cross-origin resource sharing (CORS)** | Supported | Not available. Browser-based applications must route requests through a backend proxy server. |

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we have doc links TBH that explain CORs but it's an ask from support etc. to make it clear that CORS is unsupported on serverless —JS apps running in browser can't directly call the API from web pages

Not sure if it's in scope here to explain the implications

Copy link
Contributor

Choose a reason for hiding this comment

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

We could be more precise though:

Use a backend proxy to enable integrations.
Browser-based applications must route requests through a backend proxy server.

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

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

approving to unblock hopefully pending clarification to cors implications

@leemthompo
Copy link
Contributor

thanks Shaina, have pinged the support folks and we can update in follow-up if more helpful contextual information comes to light that we could be linking to

@charlotte-hoblik you can commit Shaina's suggestion and get this merged

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

Successfully merging this pull request may close these issues.

3 participants