@czi-sds/mcp 0.3.0 → 0.4.0

package/data/zeroheight-exports/Search.md

@@ -6,16 +6,16 @@ Search is a flexible way for users to find data of interest or filter down their
 
 ## Search Flow Types
 
-| There are three general flow patterns recommended when considering adding search or filter functionality to products. Each of these follows the same four basic steps:  1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |   | **Jump to flow type:** On-page Results flow Results Page flow |
-| --- | --- | --- |
+| There are three general flow patterns recommended when considering adding search or filter functionality to products. Each of these follows the same four basic steps: 1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |     | **Jump to flow type:** On-page Results flow Results Page flow |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | ------------------------------------------------------------- |
 
 ### Flow Types
 
-| **On-page Results** |   | **Results Page** |
-| --- | --- | --- |
+| **On-page Results** |     | **Results Page** |
+| ------------------- | --- | ---------------- |
 
-| The content on the page automatically updates to reflect the search result. |   | The results of the search are displayed on a separate "search results" page. |
-| --- | --- | --- |
+| The content on the page automatically updates to reflect the search result. |     | The results of the search are displayed on a separate "search results" page. |
+| --------------------------------------------------------------------------- | --- | ---------------------------------------------------------------------------- |
 
 ---
 
@@ -23,23 +23,21 @@ Search is a flexible way for users to find data of interest or filter down their
 
 Search results are displayed on the current page by filtering down the visible content within the searchable area(s) to show matches only. This search is the most common pattern; it is used both at the component and the page levels.
 
- 
+
 
 ---
 
 #### 1. User types keyword into Search Input
 
-It is recommended to position your Search Input at the top level of the content the user will be searching. 
+It is recommended to position your Search Input at the top level of the content the user will be searching.
 
-For example, if the search will display results for a list of plugins (1), position the Search Input at the top of the list (2). 
+For example, if the search will display results for a list of plugins (1), position the Search Input at the top of the list (2).
 
 #### **2. Search Initiated by User**
 
-Search is initiated when the user clicks a button, hits “enter”, or completes some other user action. 
-
-This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search.  
+Search is initiated when the user clicks a button, hits “enter”, or completes some other user action.
 
- 
+This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search.
 
 
 
@@ -53,10 +51,10 @@ If there are no results, it is recommended that a “No Results” blank state i
 
 Depending on the product and the user’s workflow, users may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Sort search results (2).
-* Filter search results (3).
-* Interact with results, such as selecting a single result (4).
+- Refine search results (1); re-starts this flow.
+- Sort search results (2).
+- Filter search results (3).
+- Interact with results, such as selecting a single result (4).
 
 ---
 
@@ -64,7 +62,7 @@ Depending on the product and the user’s workflow, users may take a number of n
 
 Below are links to example use cases where we recommend using an On-page Results flow:
 
-* Search within a Dropdown Menu
+- Search within a Dropdown Menu
 
 ### Technical Considerations
 
@@ -72,8 +70,8 @@ It is recommended to discuss any search approach under consideration with the en
 
 That being said, for the On-page Results flow, keep in mind:
 
-* This approach is impacted by whether the search is done on the frontend or the backend. If search is slow and has to be done on the backend, consider using the Results Page flow type instead.
-* Paginated vs infinite scrolling results may have an impact on the search flow options available.
+- This approach is impacted by whether the search is done on the frontend or the backend. If search is slow and has to be done on the backend, consider using the Results Page flow type instead.
+- Paginated vs infinite scrolling results may have an impact on the search flow options available.
 
 ---
 
@@ -81,7 +79,7 @@ That being said, for the On-page Results flow, keep in mind:
 
 Search results are displayed on a different page than where the search was originally initiated. Depending on the use case, this may be a unique “Results” page, or an existing page where the data is usually located. The Results Page flow is often combined with the On-page Results flow. Learn more about Combining Search Types.
 
- 
+
 
 ---
 
@@ -91,7 +89,7 @@ It is recommended to position Search Inputs at the top level of the content the
 
 For example, if the search will display results from across the whole site (1), position the Search Input in a top-level navigation or outside of the page content hierarchy (2).
 
- 
+
 
 #### 2. **Search Initiated by User**
 
@@ -99,7 +97,7 @@ Search is initiated when the user clicks a button (1), hits “enter” (2), or
 
 Because results will be displayed on a new page, Live Search is not recommended.
 
- 
+
 
 #### 3. Results Displayed on the Results page
 
@@ -109,17 +107,17 @@ The results page format depends on the product's use case and content. In the ex
 
 If there are no results, it is recommended to display a bank state on the results page.
 
- 
+
 
 #### 4. User Takes Action on Results
 
 Depending on the product and the user’s workflow, they may take a number of next actions on the results, possibly including:
 
-* Refine search results (1). It is recommended to use the On-Page Results flow type; see Combining Flow Types.
-* Interact with results, like drilling down into a single result (2) .
-* Filter or Sort Results.
+- Refine search results (1). It is recommended to use the On-Page Results flow type; see Combining Flow Types.
+- Interact with results, like drilling down into a single result (2) .
+- Filter or Sort Results.
+
 
- 
 
 ---
 
@@ -127,7 +125,7 @@ Depending on the product and the user’s workflow, they may take a number of ne
 
 It is recommended to discuss any search approach under consideration with the engineering team to better understand the technical parameters the product can support.
 
-That being said, for the Results Page flow type, keep in mind that this approach has the best performance when the search is performed on the backend. 
+That being said, for the Results Page flow type, keep in mind that this approach has the best performance when the search is performed on the backend.
 
 ## Example Use Cases
 
@@ -143,8 +141,8 @@ The following behaviors are recommended for displaying search results within a D
 
 ## Other Considerations
 
-| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it.  The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components. |   | **Jump to pattern:** Combining Search Types Supporting User Behavior |
-| --- | --- | --- |
+| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it. The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components. |     | **Jump to pattern:** Combining Search Types Supporting User Behavior |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | -------------------------------------------------------------------- |
 
 ---
 
@@ -187,7 +185,7 @@ Search results are displayed on the current page by filtering down the visible c
 
 It is recommended to position the Search Input at the top level of the content the user will be searching within.
 
-For example, if the search will display results for a single Table (1), position the Search Input at the top of the table (2). 
+For example, if the search will display results for a single Table (1), position the Search Input at the top of the table (2).
 
 #### **2A. Search Initiated Automatically (Live Search)**
 
@@ -195,15 +193,11 @@ Otherwise known as "Live Search," as the user types, the app automatically initi
 
 This method is recommended in most cases of the On-page Results flow if implementation will allow it. This may not be a feasible solution if the product's search results are paginated.
 
-
-
 #### **2B. Search Initiated by User**
 
 Search is initiated when the user clicks a button, hits “enter”, or completes some other user action.
 
-This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search. 
-
-
+This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search.
 
 #### **3. Results Displayed in Searched Content Area**
 
@@ -211,16 +205,16 @@ Results are displayed by filtering the content in the searchable area (1) so tha
 
 If there are no results, it is recommended that a “No Results” blank state is displayed in the content area instead.
 
- 
+
 
 **4. User Takes Action on Results**
 
 Depending on the product and the user’s workflow, users may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Filter search results (2).
-* Sort search results (3).
-* Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
+- Refine search results (1); re-starts this flow.
+- Filter search results (2).
+- Sort search results (3).
+- Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
 
 ---
 
@@ -228,7 +222,7 @@ Depending on the product and the user’s workflow, users may take a number of n
 
 Below are links to example use cases where we recommend using an On-page Results flow:
 
-* Search within a Dropdown Menu
+- Search within a Dropdown Menu
 
 ### Technical Considerations
 
@@ -262,18 +256,18 @@ Search is a flexible way for users to find data of interest or filter down their
 
 ## Search Flow Types
 
-| There are two general flow patterns recommended when considering adding search or filter functionality to products. Both of these follow the same four basic steps:  1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |   | **Jump to type:** On-page Results flow Results Dropdown flow |
-| --- | --- | --- |
+| There are two general flow patterns recommended when considering adding search or filter functionality to products. Both of these follow the same four basic steps: 1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |     | **Jump to type:** On-page Results flow Results Dropdown flow |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- | ------------------------------------------------------------ |
 
 ---
 
 ### Flow Types
 
-| **On-page Results** |   | **Results Dropdown** |
-| --- | --- | --- |
+| **On-page Results** |     | **Results Dropdown** |
+| ------------------- | --- | -------------------- |
 
-| The content on the page automatically updates to reflect the search result. |   | The results of the search are Menu Items in a Dropdown Menu for the user to select from. |
-| --- | --- | --- |
+| The content on the page automatically updates to reflect the search result. |     | The results of the search are Menu Items in a Dropdown Menu for the user to select from. |
+| --------------------------------------------------------------------------- | --- | ---------------------------------------------------------------------------------------- |
 
 ---
 
@@ -295,8 +289,6 @@ Search is initiated when the user clicks a button, hits “enter”, or complete
 
 This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search.
 
-
-
 #### **3. Results Displayed in Searched Content Area**
 
 Results are displayed by filtering the content in the searchable area (1) so that only search results are visible.
@@ -307,10 +299,10 @@ If there are no results, it is recommended that a “No Results” blank state i
 
 Depending on the product and the user’s workflow, users may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Filter search results (2).
-* Sort search results (3).
-* Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
+- Refine search results (1); re-starts this flow.
+- Filter search results (2).
+- Sort search results (3).
+- Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
 
 ---
 
@@ -318,7 +310,7 @@ Depending on the product and the user’s workflow, users may take a number of n
 
 Below are links to example use cases where we recommend using an On-page Results flow:
 
-* Search within a Dropdown Menu
+- Search within a Dropdown Menu
 
 ### Technical Considerations
 
@@ -346,8 +338,6 @@ As the user types, the app automatically initiates the search with each keystrok
 
 It is not recommended for user action to initiate search for this flow type.
 
-
-
 #### **3. Results Displayed in Dropdown**
 
 Instead of updating the searched content area, results are displayed in a Dropdown Menu below the Search Input (1).
@@ -358,9 +348,9 @@ If there are no results, it is recommended to display a bank state in the Dropdo
 
 Depending on the product and the user’s workflow, they may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Interact with results, such as drilling down into a single result (2) .
-* Initiate a different type of search flow. For example, the user clicks “enter” to filter page by search keyword (3). See Combining Search Types section to learn more.
+- Refine search results (1); re-starts this flow.
+- Interact with results, such as drilling down into a single result (2) .
+- Initiate a different type of search flow. For example, the user clicks “enter” to filter page by search keyword (3). See Combining Search Types section to learn more.
 
 ## Example Use Cases
 
@@ -374,12 +364,12 @@ When searching the Menu Items within a Dropdown Menu, it is recommended to use t
 
 The following behaviors are recommended for displaying search results within a Dropdown Menu.
 
- 
+
 
 ## Other Considerations
 
-| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it.  The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components.   **Please consider the information in this section as inspiration only.** |   | **Jump to pattern:** Combining Search Types Supporting User Behavior |
-| --- | --- | --- |
+| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it. The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components. **Please consider the information in this section as inspiration only.** |     | **Jump to pattern:** Combining Search Types Supporting User Behavior |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- | -------------------------------------------------------------------- |
 
 ---
 
@@ -405,16 +395,16 @@ Search is a flexible way for users to find data of interest or filter down their
 
 ## Search Flow Types
 
-| There are three general flow patterns recommended when considering adding search or filter functionality to products. Each of these follows the same four basic steps:  1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |   | **Jump to flow type:** On-page Results flow Results Dropdown flow Results Page flow |
-| --- | --- | --- |
+| There are three general flow patterns recommended when considering adding search or filter functionality to products. Each of these follows the same four basic steps: 1. User types in a keyword 2. Search is initiated 3. Results are displayed 4. User takes action on the results Although the general steps followed are universal, the implementation choices made on how each step is accomplished, most notably how the results are displayed, are what differentiate each flow type. |     | **Jump to flow type:** On-page Results flow Results Dropdown flow Results Page flow |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- | ----------------------------------------------------------------------------------- |
 
 ### Flow Types
 
 | **On-page Results** | **Results Dropdown** | **Results Page** |
-| --- | --- | --- |
+| ------------------- | -------------------- | ---------------- |
 
 | The content on the page automatically updates to reflect the search result. | The results of the search are Menu Items in a Dropdown Menu for the user to select from. | The results of the search are displayed on a separate "search results" page. |
-| --- | --- | --- |
+| --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
 
 ---
 
@@ -430,9 +420,9 @@ The example flow below uses CZ GEN EPI to show the on-page refresh of content th
 
 #### 1. User types keyword into Search Input
 
-It is recommended to position the Search Input at the top level of the content the user will be searching within. 
+It is recommended to position the Search Input at the top level of the content the user will be searching within.
 
-For example, if the search will display results for a single Table (1), position the Search Input at the top of the table (2). 
+For example, if the search will display results for a single Table (1), position the Search Input at the top of the table (2).
 
 #### 2A. Search Initiated Automatically (Live Search)
 
@@ -440,30 +430,26 @@ Otherwise known as "Live Search," as the user types, the app automatically initi
 
 This method is recommended in most cases of the On-page Results flow if implementation will allow it. This may not be a feasible solution if the product's search results are paginated.
 
-
-
 #### **2B. Search Initiated by User**
 
-Search is initiated when the user clicks a button, hits “enter”, or completes some other user action. 
+Search is initiated when the user clicks a button, hits “enter”, or completes some other user action.
 
 This method is recommended when search results must be fetched from the backend, or when the user needs to set up other specifications before initiating the search.
 
-
-
 #### **3.** Results Displayed in Searched Content Area
 
-Results are displayed by filtering the content in the searchable area (1) so that only search results are visible. 
+Results are displayed by filtering the content in the searchable area (1) so that only search results are visible.
 
-If there are no results, it is recommended that a “No Results” blank state is displayed in the content area instead.  
+If there are no results, it is recommended that a “No Results” blank state is displayed in the content area instead.
 
 #### 4. User Takes Action on Results
 
 Depending on the product and the user’s workflow, users may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Filter search results (2).
-* Sort search results (3).
-* Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
+- Refine search results (1); re-starts this flow.
+- Filter search results (2).
+- Sort search results (3).
+- Interact with results, like drilling down into a single result, performing actions upon results, etc. (4).
 
 ---
 
@@ -471,7 +457,7 @@ Depending on the product and the user’s workflow, users may take a number of n
 
 Below are links to example use cases where we recommend using an On-page Results flow:
 
-* Search within a Dropdown Menu
+- Search within a Dropdown Menu
 
 ### Technical Considerations
 
@@ -479,14 +465,14 @@ It is recommended to discuss any search approach under consideration with the en
 
 That being said, for the On-page Results flow, keep in mind:
 
-* This approach is impacted by whether the search is done on the frontend or the backend. If search is slow and has to be done on the backend, consider using User-initiated Search (Step 2B) or the Results Page flow type instead.
-* Paginated vs infinite scrolling results may have an impact on the search flow options available. 
+- This approach is impacted by whether the search is done on the frontend or the backend. If search is slow and has to be done on the backend, consider using User-initiated Search (Step 2B) or the Results Page flow type instead.
+- Paginated vs infinite scrolling results may have an impact on the search flow options available.
 
 ---
 
 ## Results Dropdown
 
-Search results are displayed inside a Dropdown Menu that appears below the Search Input. The user will remain on the same page until they select a result from the Dropdown Menu. 
+Search results are displayed inside a Dropdown Menu that appears below the Search Input. The user will remain on the same page until they select a result from the Dropdown Menu.
 
 ### Example from CZ ID
 
@@ -498,7 +484,7 @@ The example flow below uses CZ ID to show the contents of a Dropdown Menu filter
 
 It is recommended to position the Search Input at the top level of the content the search will apply to.
 
-For example, if the search will display results from across multiple tabs (1), position the Search Input in the header (2). 
+For example, if the search will display results from across multiple tabs (1), position the Search Input in the header (2).
 
 #### 2. Search Initiated (Live Update)
 
@@ -506,11 +492,9 @@ As the user types, the app automatically initiates the search with each keystrok
 
 It is not recommended for user action to initiate search for this flow type.
 
-
-
 #### 3. Results Displayed in Dropdown
 
-Instead of updating the searched content area, results are displayed in a Dropdown Menu below the Search Input (1). 
+Instead of updating the searched content area, results are displayed in a Dropdown Menu below the Search Input (1).
 
 If there are no results, it is recommended to display a bank state in the Dropdown Menu instead.
 
@@ -518,9 +502,9 @@ If there are no results, it is recommended to display a bank state in the Dropdo
 
 Depending on the product and the user’s workflow, they may take a number of next actions on the results, possibly including:
 
-* Refine search results (1); re-starts this flow.
-* Interact with results, such as drilling down into a single result (2) .
-* Initiate a different type of search flow. For example, the user clicks “enter” to filter page by search keyword (3). See Combining Search Types section to learn more. 
+- Refine search results (1); re-starts this flow.
+- Interact with results, such as drilling down into a single result (2) .
+- Initiate a different type of search flow. For example, the user clicks “enter” to filter page by search keyword (3). See Combining Search Types section to learn more.
 
 ---
 
@@ -536,21 +520,21 @@ The example flow below uses napari.org to show the usage of a Results Page to di
 
 #### 1. User Types Keyword into Search Component
 
-It is recommended to position Search Inputs at the top level of the content the search will apply to. 
+It is recommended to position Search Inputs at the top level of the content the search will apply to.
 
 For example, if the search will display results from across the whole site (1), position the Search Input in a top-level navigation or outside of the page content hierarchy (2).
 
 #### 2. **Search Initiated by User**
 
-Search is initiated when the user clicks a button (1), hits “enter” (2), or some other user action. 
+Search is initiated when the user clicks a button (1), hits “enter” (2), or some other user action.
 
 Because results will be displayed on a new page, Live Search is not recommended.
 
 #### 3. Results Displayed on the Results page
 
-After the user initiates the search, they are automatically directed to a results page. 
+After the user initiates the search, they are automatically directed to a results page.
 
-The results page format depends on the product's use case and content. In the example shown, the results page is a unique page that lists search results for pages across the entire website.  
+The results page format depends on the product's use case and content. In the example shown, the results page is a unique page that lists search results for pages across the entire website.
 
 If there are no results, it is recommended to display a bank state on the results page.
 
@@ -558,9 +542,9 @@ If there are no results, it is recommended to display a bank state on the result
 
 Depending on the product and the user’s workflow, they may take a number of next actions on the results, possibly including:
 
-* Refine search results (1). It is recommended to use the On-Page Results flow type; see Combining Flow Types.
-* Interact with results, like drilling down into a single result (2) .
-* Filter or Sort Results.
+- Refine search results (1). It is recommended to use the On-Page Results flow type; see Combining Flow Types.
+- Interact with results, like drilling down into a single result (2) .
+- Filter or Sort Results.
 
 ---
 
@@ -568,7 +552,7 @@ Depending on the product and the user’s workflow, they may take a number of ne
 
 It is recommended to discuss any search approach under consideration with the engineering team to better understand the technical parameters the product can support.
 
-That being said, for the Results Page flow type, keep in mind that this approach has the best performance when the search is performed on the backend. 
+That being said, for the Results Page flow type, keep in mind that this approach has the best performance when the search is performed on the backend.
 
 ## Example Use Cases
 
@@ -584,8 +568,8 @@ The following behaviors are recommended for displaying search results within a D
 
 ## Other Considerations
 
-| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it.  The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components.   **Please consider the information in this section as inspiration only.** |   | **Jump to pattern:** Combining Search Types Supporting User Behavior |
-| --- | --- | --- |
+| Search is a complex component, and is highly subjective to each product's use case. While it's impossible to support and document every use case, here is a collection of patterns that may be useful to consider when implementing it. The patterns detailed below have not been developed by the SDS team and are simply examples pulled from products that utilize the SDS components. **Please consider the information in this section as inspiration only.** |     | **Jump to pattern:** Combining Search Types Supporting User Behavior |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- | -------------------------------------------------------------------- |
 
 ---
 
@@ -595,7 +579,7 @@ Depending on the use case, there may be a need to combine multiple flow types. H
 
 ### Results Page + On-page Results Flow
 
-In most use cases for the Results Page flow, it can be beneficial to provide users with a way to modify their search results by implementing the On-page Results flow within a Results Page design. 
+In most use cases for the Results Page flow, it can be beneficial to provide users with a way to modify their search results by implementing the On-page Results flow within a Results Page design.
 
 ### Results Dropdown + On-page Results Flow
 
@@ -606,4 +590,3 @@ CZ ID combines the Results Dropdown and the On-page Results flows. This allows u
 ## Patterns to Support User Behavior
 
 Below are some example behavior patterns worth considering to help support users in their searching. Evaluate if implementing these will help users’ workflows and if the product can support any technical requirements of implementation.
-