Automattic / Automattic/jetpack

Search: Expanded Results needs better fallbacks for "empty-ish" content

Open
#16,383 1 comment 0 reactions 0 assignees View on GitHub
[Feature] Search [Status] Needs Design
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

I think we should think about better fallbacks for empty content with the expanded results. This is what it looks like when I import a bunch of content:

Screen Shot 2020-07-03 at 10 26 11 AM

Screen Shot 2020-07-03 at 10 31 01 AM

Screen Shot 2020-07-03 at 10 31 32 AM

This is on https://gibrownatomictest.wpcomstaging.com/ where I used the test Woo sample data from https://docs.woocommerce.com/document/importing-woocommerce-sample-data/

Compare this to the minimal view (also not great, but feels less broken):

Screen Shot 2020-07-03 at 10 33 49 AM

A site that is full of this is certainly not likely, but it probably is very likely that some content will look like that so I think we need to handle it better. As is, it feels broken. Some ideas:
- I don't think we are showing the categories and tags as fallbacks
- Maybe we can improve indexing: home page should show site title and subtitle. Pull in header image?
- Can we improve the breadcrumbs? The storefront theme actually uses:

Screen Shot 2020-07-03 at 10 37 36 AM

Contributor guide

Open the contributing guide

Research direction

Start by reproducing Expanded Results on the staging site with the WooCommerce sample data, then compare it with the minimal view and the Storefront theme breadcrumbs shown in the issue. Define better fallbacks for empty content, including the categories, tags, site title, subtitle, header image, and breadcrumbs described in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
frontend, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.