visibility pg refactor (#5039)

* visibility pg split

* change header levels and less duplication

* Remove in this guide 

Removed the guide section TOC listing various visibility stores.

Author: jsundai

docs/encyclopedia/visibility/dual-visibility.mdx

@@ -21,7 +21,7 @@ This page discusses [Dual Visibility](#dual-visibility).
 ## What is Dual Visibility? {/* #dual-visibility */}
 
 Dual Visibility is a feature that lets you set a secondary Visibility store in addition to a primary store in your Temporal Service.
-Setting up Dual Visibility is optional and can be used to [migrate your Visibility database](/self-hosted-guide/visibility#migrating-visibility-database) or create a backup Visibility store.
+Setting up Dual Visibility is optional and can be used to [migrate your Visibility database](/self-hosted-guide/visibility/migrate) or create a backup Visibility store.
 
 For example, if you have Cassandra configured as your Visibility database, you can set up a supported SQL database as your secondary Visibility store and gradually migrate your data to the secondary store before deprecating your primary one.
 
@@ -30,7 +30,7 @@ A Dual Visibility setup requires two Visibility store configurations:
 - **Primary Visibility:** The primary Visibility store where Visibility data is written to and read from by default. The primary Visibility store is set with the `visibilityStore` configuration key in your Temporal Service.
 - **Secondary Visibility:** A secondary storage for your Visibility data. The secondary Visibility store is set with the `secondaryVisibilityStore` configuration key in your Temporal Service.
 
-For configuration details, see [Dual Visibility setup](/self-hosted-guide/visibility#dual-visibility).
+For configuration details, see [Dual Visibility setup](/self-hosted-guide/visibility/dual-visibility).
 
 The following combinations are allowed in a Dual Visibility setting.
 
@@ -44,4 +44,4 @@ With Dual Visibility, you can read from only one Visibility store at a time, but
 When migrating from one Visibility store database to another, set up the database you want to migrate to as your secondary Visibility store.
 
 You can plan your migration using specific dynamic configuration keys that help you transition your read and write operations from the primary to the secondary Visibility store.
-For details on migrating your Visibility store databases, see [Dual Visibility](/self-hosted-guide/visibility#dual-visibility).
+For details on migrating your Visibility store databases, see [Dual Visibility](/self-hosted-guide/visibility/dual-visibility).

docs/encyclopedia/visibility/list-filter.mdx

@@ -27,7 +27,7 @@ A List Filter includes [Search Attribute](/search-attribute) names, Search Attri
 List Filter [Search Attribute](/search-attribute) names are case sensitive.
 A single [Namespace](/namespaces) scopes each List Filter.
 
-A List Filter using a time range provides a resolution of 1 ns on [Elasticsearch](/self-hosted-guide/visibility#elasticsearch) and 1 µs for [SQL databases](/self-hosted-guide/visibility).
+A List Filter using a time range provides a resolution of 1 ns on [Elasticsearch](/self-hosted-guide/visibility/elasticsearch) and 1 µs for [SQL databases](/self-hosted-guide/visibility).
 
 ### Supported operators
 

docs/encyclopedia/visibility/search-attributes.mdx

@@ -127,14 +127,14 @@ You can use the default Search Attributes in a List Filter, such as in the Tempo
 
 ### Custom Search Attributes {/* #custom-search-attribute */}
 
-You can [create custom Search Attributes](/self-hosted-guide/visibility#create-custom-search-attributes) with unique key names that are relevant to your business needs.
+You can [create custom Search Attributes](/self-hosted-guide/visibility/custom-search-attributes#create-custom-search-attributes) with unique key names that are relevant to your business needs.
 
 Use custom Search Attributes in a List Filter, such as in the Temporal Web UI or with the `temporal workflow list` commands, under the following conditions:
 
 - Without advanced Visibility, you cannot use a custom Search Attribute in your List Filter.
 - With advanced Visibility, you can create multiple custom Search Attributes and use them in combinations with List Filters to get a list of specific Workflow Executions.
   For example: `temporal workflow list --query "WorkflowType = 'main.YourWorkflowDefinition' and YourCustomSA = 'YourCustomSAValue' and (StartTime > '2022-06-07T16:46:34.236-08:00' or CloseTime < '2022-06-08T16:46:34-08:00')"`
-  - With Temporal Server v1.19 and earlier, you must [integrate Elasticsearch](/self-hosted-guide/visibility#elasticsearch) to use custom Search Attributes with List Filters.
+  - With Temporal Server v1.19 and earlier, you must [integrate Elasticsearch](/self-hosted-guide/visibility/elasticsearch) to use custom Search Attributes with List Filters.
   - With Temporal Server v1.20 and later, custom Search Attribute capabilities are available on MySQL (v8.0.17 or later), PostgreSQL (v12 and later), and SQLite (v3.31.0 and later), in addition to Elasticsearch.
 
 If you use Elasticsearch as your Visibility store, your custom Search Attributes apply globally and can be used across Namespaces.
@@ -256,8 +256,8 @@ For Temporal Cloud specific configurations, see the [Defaults, limits, and confi
 Search Attributes available in your Visibility store can be used with Workflow Executions for the Temporal Service.
 To actually have results from the use of a [List Filter](/list-filter), Search Attributes must be added to a Workflow Execution as metadata.
 
-- To create custom Search Attributes in your Visibility store, see [Create custom Search Attributes](/self-hosted-guide/visibility#create-custom-search-attributes).
-- To remove a custom Search Attribute from the Visibility store, see [Remove custom Search Attributes](/self-hosted-guide/visibility#remove-custom-search-attributes).
+- To create custom Search Attributes in your Visibility store, see [Create custom Search Attributes](/self-hosted-guide/visibility/custom-search-attributes#create-custom-search-attributes).
+- To remove a custom Search Attribute from the Visibility store, see [Remove custom Search Attributes](/self-hosted-guide/visibility/custom-search-attributes#remove-custom-search-attributes).
   Removing custom Search Attributes is not supported on Temporal Cloud.
 - To rename a custom Search Attribute on Temporal Cloud, see [`tcld namespace search-attributes rename`](/cloud/tcld/namespace/#rename).
 

docs/encyclopedia/visibility/visibility.mdx

@@ -89,4 +89,4 @@ Prior to Temporal Server v1.20, Temporal had two Visibility modes: "standard" an
 
 Starting with Temporal Server v1.20, advanced Visibility became available on SQL databases. Standard Visibility was deprecated in v1.21 and removed in v1.24. All current deployments use what was formerly called advanced Visibility, now simply called Visibility.
 
-If you are running a Temporal Server version older than v1.24, see the [legacy standard Visibility section](/self-hosted-guide/visibility#legacy-standard-visibility) in the self-hosted guide.
+If you are running a Temporal Server version older than v1.24, see the [legacy standard Visibility section](/self-hosted-guide/visibility/legacy-standard) in the self-hosted guide.