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

[BUG][WEBSITE] Using Search via o3de.org homepage nav creates a different experience #1201

Open
amzn-leenguy opened this issue Nov 18, 2021 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/website Categorizes an issue or PR as related to the website itself. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/major Major priority. Work that should be handled after all blocking and critical work is done. RTE (Temp) Denotes an issue related to the Rev the Engine program

Comments

@amzn-leenguy
Copy link
Contributor

Describe the bug

When a user uses the search field that's embedded into the main nav on o3de.org, it creates a different experience, and allows the user to create new search queries. (Something that is not available on the current workflow if someone uses the search field on the o3de.org/docs/ website.

There are some bugs that come with this:

  • *[Minor] *When you search via the home page search field, it retains the nav from home page. allowing the user to query again. Ideally we want users to have the proper nav that is present on the o3de.org/docs website when using the docs website.
  • *[Major] *Searching doesn’t scroll the user to the top of the page after new search queries. causes confusing experience.

Reproduction steps

  1. Goto o3de.org
  2. Click on the search icon in the nav
  3. type in a query
  4. It loads the search results, but the o3de.org nav is still present.
  5. (This is a different experience)

Expected behavior

That typing in a keyword into the search field on the home nav, will just input that query into the search field that is present in the o3de.org/docs search field and carry the user through that same experience.

Screenshots

SEARCHING VIA O3DE.ORG HOMEPAGE (With incorrect nav)

Screen Shot 2021-11-18 at 2 57 27 PM

SEARCHING VIA O3DE.ORG/DOCS website field (with correct nav)

Screen Shot 2021-11-18 at 2 57 46 PM

Other information

NA

@amzn-leenguy amzn-leenguy added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Nov 18, 2021
@chanmosq chanmosq added kind/bug Categorizes issue or PR as related to a bug. priority/major Major priority. Work that should be handled after all blocking and critical work is done. RTE (Temp) Denotes an issue related to the Rev the Engine program WF8 This is a temporary label that will be removed once data conversion is complete and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 24, 2021
@chanmosq
Copy link
Contributor

Requires technical fix in the website infrastructure.

@chanmosq chanmosq removed the WF8 This is a temporary label that will be removed once data conversion is complete label Nov 24, 2021
@yuyihsu yuyihsu added the kind/website Categorizes an issue or PR as related to the website itself. label Dec 6, 2021
@micronAMZN micronAMZN added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/website Categorizes an issue or PR as related to the website itself. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/major Major priority. Work that should be handled after all blocking and critical work is done. RTE (Temp) Denotes an issue related to the Rev the Engine program
Projects
None yet
Development

No branches or pull requests

4 participants