Revert "updated best practices header and changed portal references to DX"

This reverts commit 35cfb96e945707f93f9030fee0f395e604927021.

Author: marcvincentvista

docs/.pages

@@ -7,4 +7,5 @@ nav:
     - manage_content
     - extend_dx
     - guide_me
-    - early_access
+    - early_access
+    - DX Compose: https://help.hcl-software.com/digital-experience/dx-compose/latest/

docs/assets/HCL_Search_Get_Theme_Modules_12.png

@@ -1,18 +1,16 @@
 # Configuring Web Content Manager search options
 
-You can edit the following search options to manage how the search service works with Web Content Manager search forms.
+Configure the **WCM SearchService** search properties from the WebSphere Integrated Solutions Console to manage how the search service works with Web Content Manager search forms.
 
-You can edit the following search options to manage how the search service works with Web Content Manager search forms
-
-1.  Open WebSphere Integrated Solutions Console to configure the **WCM SearchService** properties. Go to **Resources** \> **Resource Environment** \> **Resource Environment Providers**.
+1.  Go to **Resources** \> **Resource Environment** \> **Resource Environment Providers**.
 
 2.  Select **WCM SearchService, Custom** properties.
 
 3.  Specify values for the search parameters.
 
     -   **SearchService.DateFormatString**
 
-        This parameter is used to set the date format when dates are entered in search forms. Enter a supported Java date format string. If this property is not set, then the default format is `MMM dd yyyy HH:mm:ss z`.
+        Use this parameter to set the date format when dates are entered in search forms. Enter a supported Java date format string. If this property is not set, then the default format is `MMM dd yyyy HH:mm:ss z`.
 
     -   **SearchService.RecrawlInterval**
 
@@ -24,7 +22,7 @@ You can edit the following search options to manage how the search service works
 
     -   **SearchService.MetaFields**
 
-        This parameter is used to specify extra elements to crawl when searching for metadata.
+        Use this parameter to specify extra elements to crawl when searching for metadata.
 
         The format for this parameter value is: `elementName,key1`
 
@@ -34,14 +32,14 @@ You can edit the following search options to manage how the search service works
         elementName1,key1;elementName2,key2;elementName3,key3
         ```
 
-        For example, to crawl for metadata in a text element named metaText:
+        For example, to crawl for metadata in a text element named `metaText`:
 
-        -   ```
-SearchService.MetaFields=metaText,meta
-```
+        ```
+        SearchService.MetaFields=metaText,meta
+        ```
 
-        -   `elementName` is the name of element you would like to search for metadata. Any valid element with that name in a searchable site area or content item is crawled.
-        -   `key` is the "key" that is specified in an element tag that is used as part of a search element design. In the previous example, the key of "meta" is used. To render the content of the metaText element in a search element design, you would use the following tag: `<Element context="autoFill" type="content" key="meta"/>`
+        -   `elementName` is the name of the element you would like to search for metadata. Any valid element with that name in a searchable site area or content item is crawled.
+        -   `key` is the key specified in an element tag that is used as part of a search element design. In the previous example, the key `meta` is used. To render the content of the `metaText` element in a search element design, use the following tag: `<Element context="autoFill" type="content" key="meta"/>`
 
         !!! note
             -   Only text elements and short text elements can be searched.
@@ -50,22 +48,23 @@ SearchService.MetaFields=metaText,meta
     -   **SearchService.SearchSeed.ExcludeFileAttachments**
 
         Set this parameter to `true` to prevent file resource component attachments from being included in the search results.
-
-        If set to false, the files that are stored in file resource elements in content items can also be searched. Files that are stored in file resource elements in a site area can also be searched so long as a default content item is selected.
+        
+        Set this parameter to `false` to make files stored in file resource elements in content items searchable. Files stored in file resource elements in a site area also become searchable if a default content item is selected.
 
     -   **SearchService.SearchSeed.excludeExtensions**
 
         Set this parameter to a list of file name extensions that you want to exclude from search results. Separate each item in the list with a comma. Any file resource component attachments and file resource element attachments that have these extensions are excluded from search results. For example, `SearchService.SearchSeed.excludeExtensions=avi,mpeg,zip`.
 
     -   **Searchservice.searchseed.excludeContentResourceTypeElement**
 
-        Set this parameter to true to exclude the default file resource element of a content item which is set to resource type from the seedlist, since the default file resource element is already being pointed to by the content item. The default setting is false.
+        Set this parameter to `true` to exclude the default file resource element of a content item that is already included through its resource type from the seedlist. The default file resource element is excluded since it is already being pointed to by the content item. The default setting is `false`.
 
-4.  Click **Apply** and then **OK**.
+    -   **Searchservice.SearchSeed.excludeFields**
 
-5.  Restart the portal for the new settings to take effect.
-
-6.  Delete and create a new search collection for changes to take effect.
+        Set this parameter to a list of meta fields you want to exclude from the search seedlist.
 
+4.  Click **Apply** > **OK**.
 
+5.  Restart the portal for the new settings to take effect.
 
+6.  Delete and create a new search collection for changes to take effect.

docs/assets/HCL_Search_Get_Theme_Modules_13.png

@@ -9,6 +9,7 @@ Search seedlist 1.0 can make access control information available in a way that
 !!! important
     When changing access control on libraries or setting access on the library root, note that seedlist requests relative to a timestamp will not list items affected by an access control change. To retrieve those updates, it is recommended to trigger a full crawl. 
     DX classic Search, either local or remote, uses post-access control filtering and is therefore not affected.
+    Starting CF225, you can have the seedlist return items affected by library access control changes. To enable this feature, set ```seedlistUpdateLibrariesForAccessControl=true``` in `WCM WCMConfigService`.
 
 
 -   **[The search seedlist 1.0 format](../crawling_webcontent_seedbase/wcm_searchseed/index.md)**  

docs/assets/HCL_Search_Theme_Analyzer.png

@@ -4,7 +4,7 @@
 
 This topic provides information on how you can improve search quality in HCL Digital Experience and Web Content Manager Search.
 
-The quality of search is based primarily on the relevance scoring methods within HCL Digital Experience and the Web Content Manager Search component. The search applies standard relevance calculation provided by the underlying open source [Lucene search engine](http://http//lucene.apache.org). 
+The quality of search is based primarily on the relevance scoring methods within HCL Digital Experience and the Web Content Manager Search component. The search applies standard relevance calculation provided by the underlying open source [Lucene search engine](https://lucene.apache.org){target="_blank"}. 
 
 In general, terms are based on standard scoring **“tf x idf”** (term frequency times inverted document frequency). The structure of information provided in a document is not considered. For example, whether a keyword is found in the 'title' or any other structural element of the document. When a keyword appears in the title, it is assumed that this keyword is significant for this document as opposed to that same keyword appearing only in the document's regular body text. This section describes what search quality tuning options are available to improve the search quality.
 

docs/assets/HCL_Search_Theme_Analyzer_New_Module.png

@@ -6,3 +6,4 @@ nav:
     - Using Search V2: usage.md
     - Limitations of Search V2: limitations.md
     - Components of Search V2: components.md
+    - Customizations for Search V2: customizations.md

docs/build_sites/search/cfg_dx_search/wcm_config_search.md

@@ -230,113 +230,6 @@ Functional Composite Components (FCC) combine ACs to deliver higher-level functi
     |**searchResults** |	DxSearchResults	| Contains the search results, including hit count, individual hits, and scores. |	{ hits: { total: { value: NaN, relation: 'eq' }, max_score: 0, hits: [] } } |
     |**isLoading** |	Boolean	| A flag that indicates whether search results are being loaded. |	false |
 
-## Styling the search components
-
-This section explains the default styles for search components and how to customize them.
-
-### Default styling
-
-Each component comes with default styles. See the following examples of different default styles below.
-
-```scss
-/* for dx-search-center-layout */
-dx-search-center-layout::part(main) {
-  display: flex;
-}
-/* for dx-input-textfield */
-dx-input-textfield::part(div) {
-  width: 100%;
-  position: relative;
-}
-/* for dx-button */
-dx-button::part(button) {
-  @include button;
-}
-/* for dx-circular-progress */
-@keyframes rotateCircularProgress {
-  100% {
-   transform: rotate(360deg);
-  }
-}
-/* for dx-header */
-dx-header::part(div) {
-  width: 100%;
-  position: relative;
-}
-/* for dx-chip */
-dx-chip::part(chip-div) {
-  background-color: $BLACK8P;
-  border-radius: 4px;
-  display:inline-flex;
-  padding:8px 8px 8px 8px;
-  align-items: center;
-  height: 16px;
-}
-/* for dx-avatar */
-dx-avatar::part(avatar-div) {
-  height: 32px;
-  width: 32px;
-  border: 1px solid $avatar-border-color;
-  box-sizing: border-box;
-  display: flex;
-  justify-content: center;
-  align-items: center;
-}
-// for the input select fields
-dx-search-center-layout .search-input-div {
-  display: flex;
-  flex-direction: row;
-  justify-content: space-between;
-
-  dx-search-input-scope,
-  dx-search-input-type {
-    display: flex;
-    align-self: center;
-    max-width: 49%;
-    width: 49%;
-  }
-}
-// for the input query field and button
-dx-search-center-layout div.search-input-div {
-  display: flex;
-  flex-direction: row;
-  justify-content: space-between;
-
-  dx-search-input-query {
-    display: flex;
-    align-self: center;
-    width: calc(100% - 125px);
-    max-width: calc(100% - 125px);
-  }
-```
-
-
-### Style customization
-
-You can override styles by targeting the component's class names. Other components can be overridden in a similar manner. Refer to the styling examples below for `dx-button` and `dx-input-textfield`.
-
-!!! note
-    The `part` attribute is used to name parts of a shadow tree, which can then be styled from outside the shadow DOM using the `::part()` pseudo-element. This allows you to apply CSS styles to shadow tree elements from the parent DOM.
-
-```css
-/* for dx-button */
-dx-button::part(button-start-icon) {
-  color: #FBCD00;    /* change the color as per your requirements and also other things can be changed */
-  height: 16px;
-  margin-right: 4px;
-  width: 16px;
-}
-/* for dx-input-textfield */
-dx-input-textfield::part(label) {
-  @include font-default;
-  width: 100%;
-  margin-bottom: 16px;
-  display: red;
-  color: #AFC002;
-}
-
-```
-
 ## Theme modules
 
 Search components are provided using theme modules, allowing users to create custom stylesheets for all components. This flexibility is ideal for adapting the search functionality to match your application's design. For more information about themes and skins in DX, refer to  [Developing themes and skins](../../build_sites/themes_skins/index.md).
@@ -400,44 +293,11 @@ You can use the default theme modules (CSS and JS files) provided to you as-is,
 
     ![](../../assets/HCL_Search_Get_Theme_Modules_12.png "Open the `default.css` file you have downloaded in a code editor such as Visual Studio Code")
 
-    See the sample view of the formatted CSS file.
+    See the sample view of the formatted `default.css` file.
 
     ![](../../assets/HCL_Search_Get_Theme_Modules_13.png "Log in to HCL Digital Experience 9.5 and Go to the Search V2 UI")
 
 
-## Using and customizing the theme modules
-
-Follow these steps to use the theme module files you downloaded on your new or existing theme pages.
-
-!!!note
-    Ensure you have downloaded the `dx_search_css` and `dx_search_js` files from [Getting the default theme modules](#getting-the-default-theme-modules) and saved the files as `default.css` and `index.js` respectively.
-
-1. Open the `default.css` file and update the styles in the file as needed. 
-
-- You can also create your own CSS file, such as `custom-theme.css`, where you can add your overrides, using the `default.css` as your guide for the base styles.
-
-2. Link the default and custom CSS files in your application's HTML code as follows.
-
-    ```html 
-      <link rel="stylesheet" href="/path/to/default.css"> 
-      <link rel="stylesheet" href="/path/to/custom-theme.css"> 
-    ```
-
-3. Download the default theme CSS `dx_search_js` from the provided location as `index.js`.
-
-4. Add the script to your application's html head.
-    ```html 
-      <script type="module" src="/path/to/index.js"></script>
-    ```
-
-    See the sample customized CSS code which changed the background color dx-search-center-layout component.
-
-    ```css
-    dx-search-center-layout::part(main) {
-        background-color: #f0f0f0;
-    }
-    ```
-
 ## Communication between components using the Broadcast Channel API
 
 Search V2 utilizes the Broadcast Channel API for its components. The Broadcast Channel API provides real-time synchronization, updating search search results when a new query is entered. It has a decoupled design that allows FCC components to work independently and communicate without direct references.