We've just implemented our product page and are moving on to the search page. Both are similar in the sense that both have blocks that are unique in this context. We will explore this block in a disorderly fashion for now, just to get an idea of its behavior. Then, we'll look at improving the layout.
Search Layout
Same as other templates, store.search can also be flexible. To build a unique layout you'll need to use a block called search-result-layout.
The search-result-layout, in turn, must receive 3 other blocks:
search-result-layout.desktop
search-result-layout.mobile
search-not-found-layout
As you've already notice, the first two define which layout will be displayed on desktop and mobile respectively, while the third defines the layout of the no results found search page.
In the course, we'll focus on desktop layout implementation.
Search blocks
The search results documentation offers a good reference for blocks that can be use in a search context. This step will focus on highlighting the main ones:
Search breadcrumb (breadcrumb.search);
Search title (search-title.v2);
Total products found (total-products.v2);
Product ordering (order-by.v2);
Show more results button (search-fetch-more);
Show previous results button (search-fetch-previous);
Navigation filter (filter-navigator.v3);
Search results (search-content)
Although quite many, all these blocks are relatively simple and work very well without an express need to configure their props.
Activity
Copy the code above in search.jsonc and define a search-result-layout.desktop with the following characteristics:
Pagination type such as 'Show more' (more on the pagination prop here);
Having the following, in the order mentioned below:
breadcrumb.search;
search-title.v2;
total-products.v2;
order-by.v2;
search-fetch-previous;
search-content;
filter-navigator.v3;
search-fetch-more.
:information_source: Remember to go through the Search Result documentation if you have any questions during the activity.
If you're still unsure as to how to send your answers, click here.
github-learning-lab[bot]
commented
4 years ago
Search page
:sparkles: Branch: search
Introduction
We've just implemented our product page and are moving on to the search page. Both are similar in the sense that both have blocks that are unique in this context. We will explore this block in a disorderly fashion for now, just to get an idea of its behavior. Then, we'll look at improving the layout.
Search Layout
Same as other templates,
store.searchcan also be flexible. To build a unique layout you'll need to use a block calledsearch-result-layout.The
search-result-layout, in turn, must receive 3 other blocks:search-result-layout.desktopsearch-result-layout.mobilesearch-not-found-layoutAs you've already notice, the first two define which layout will be displayed on desktop and mobile respectively, while the third defines the layout of the no results found search page.
In the course, we'll focus on desktop layout implementation.
Search blocks
The search results documentation offers a good reference for blocks that can be use in a search context. This step will focus on highlighting the main ones:
breadcrumb.search);search-title.v2);total-products.v2);order-by.v2);search-fetch-more);search-fetch-previous);filter-navigator.v3);search-content)Although quite many, all these blocks are relatively simple and work very well without an express need to configure their
props.Activity
Copy the code above in
search.jsoncand define asearch-result-layout.desktopwith the following characteristics:paginationprop here);Having the following, in the order mentioned below:
breadcrumb.search;search-title.v2;total-products.v2;order-by.v2;search-fetch-previous;search-content;filter-navigator.v3;search-fetch-more.:information_source: Remember to go through the Search Result documentation if you have any questions during the activity.
If you're still unsure as to how to send your answers, click here.