fix(explorer): update links to new website

src/explorer/src/content/docs/docs/index.md

@@ -18,16 +18,16 @@ Geocoding allows you to get the geographic location (i.e., the geographical coor
 
 ### Searching
 
-Searching allows you to search through more than 1,000,000 rows of [State Geographic Information Datasource](https://gis.utah.gov/sgid) (SGID) data. With over **300** layers of real-world data that you can run queries against in the SGID, you will be able to extract actionable information for your data. The UGRC API endpoint for searching allows you to:
+Searching allows you to search through more than 1,000,000 rows of [State Geographic Information Datasource](https://gis.utah.gov/documentation/sgid/) (SGID) data. With over **300** layers of real-world data that you can run queries against in the SGID, you will be able to extract actionable information for your data. The UGRC API endpoint for searching allows you to:
 
 - Get the attributes of spatial data based on a T-SQL like query.
 - Get the attributes of spatial data based on a location (i.e., spatial intersection).
 
-To view the SGID tables that are accessible through the search endpoint, [connect to the OpenSGID](https://gis.utah.gov/sgid/open-sgid/). You can then browse everything that UGRC has to offer for the State of Utah.
+To view the SGID tables that are accessible through the search endpoint, [connect to the OpenSGID](https://gis.utah.gov/documentation/sgid/open-sgid/). You can then browse everything that UGRC has to offer for the State of Utah.
 
 ### Meta
 
 The informational endpoints allow you to inspect and learn about SGID data. If you do not wish to connect to the OpenSGID, you can learn about the same data through the API. The UGRC API endpoints for information allow you to:
 
-- Get a list of table names from our [data categories](https://gis.utah.gov/data/#data-categories).
+- Get a list of table names from our [data categories](https://gis.utah.gov/products/sgid/categories/).
 - Get a list of attribute names from a table.

src/explorer/src/content/docs/docs/v1/endpoints/geocoding.mdx

@@ -20,7 +20,7 @@ Geocoding allows you to get the geographic location (i.e., the geographical coor
 1. This endpoint confirms that an address **can** exist along a road, however, there may be no structure or mail delivery at the address.
 1. This endpoint should not be used to validate mailing addresses.
 1. [Reserved characters](https://www.rfc-editor.org/rfc/rfc3986#section-2.1), like ?, #, @, etc. in your data need to be escaped or the request will fail.
-1. `matchAddress` returns the name of the [address system quadrant](https://gis.utah.gov/data/location/address-data/#AddressSystemQuadrants) for the address. For example, `"matchAddress": "10420 E Little Cottonwood Canyon, Salt Lake City"` means that the address is part of the **Salt Lake City** address system. It is neither within the boundaries of Salt Lake City proper, nor is it the preferred mailing address placename.
+1. `matchAddress` returns the name of the [address system quadrant](https://gis.utah.gov/products/sgid/location/address-system-quadrants/) for the address. For example, `"matchAddress": "10420 E Little Cottonwood Canyon, Salt Lake City"` means that the address is part of the **Salt Lake City** address system. It is neither within the boundaries of Salt Lake City proper, nor is it the preferred mailing address placename.
 
 :::
 
@@ -71,7 +71,7 @@ This option determines if the system should find a location for P.O. Box address
 
 ### locators
 
-The locators are the search engine for address data. There are three options. The default value of `all` will use the highest score from the [address point](https://gis.utah.gov/data/location/address-data/#AddressPoints) and [road centerline](https://gis.utah.gov/data/transportation/roads-system/#RoadCenterlines) data and provide the best match rate. Address point locations are used in the event of a tie. Address points are a work in progress with the counties to map structures or places where mail is delivered. Road centerlines are a dataset with every road and the range of numbers that road segment contains.
+The locators are the search engine for address data. There are three options. The default value of `all` will use the highest score from the [address point](https://gis.utah.gov/products/sgid/location/address-points/) and [road centerline](https://gis.utah.gov/products/sgid/transportation/road-centerlines/) data and provide the best match rate. Address point locations are used in the event of a tie. Address points are a work in progress with the counties to map structures or places where mail is delivered. Road centerlines are a dataset with every road and the range of numbers that road segment contains.
 
 - **Type**: `string`
 - **Default**: `all`

src/explorer/src/content/docs/docs/v1/endpoints/searching.mdx

@@ -12,7 +12,7 @@ import SpatialReference from "../../../../../components/parameters/SpatialRefere
 import OutputFormat from "../../../../../components/parameters/OutputFormat.mdx";
 import Callback from "../../../../../components/parameters/Callback.mdx";
 
-Searching allows you to find information in more than 1,000,000 rows of spatial [State Geographic Information Datasource](https://gis.utah.gov/sgid/) (SGID) data without expensive software or licensing. With over 300 tables of real-world Utah data that you can run queries against in the SGID, the possibilities can be a little overwhelming. But the searching endpoint opens the opportunity for copious information extraction. This UGRC API endpoint allows you to get geometries and attributes from any table in the [OpenSGID](https://gis.utah.gov/sgid/#open-sgid).
+Searching allows you to find information in more than 1,000,000 rows of spatial [State Geographic Information Datasource](https://gis.utah.gov/documentation/sgid/) (SGID) data without expensive software or licensing. With over 300 tables of real-world Utah data that you can run queries against in the SGID, the possibilities can be a little overwhelming. But the searching endpoint opens the opportunity for copious information extraction. This UGRC API endpoint allows you to get geometries and attributes from any table in the [OpenSGID](https://gis.utah.gov/documentation/sgid/open-sgid/).
 
 ## URI Format
 
@@ -24,7 +24,7 @@ Searching allows you to find information in more than 1,000,000 rows of spatial
 
 ### table
 
-The schema qualified name of an OpenSGID table. Read the [getting connected guide](https://gis.utah.gov/sgid/open-sgid/) to start browsing the OpenSGID.
+The schema qualified name of an OpenSGID table. Read the [getting connected guide](https://gis.utah.gov/documentation/sgid/open-sgid/) to start browsing the OpenSGID.
 
 - **Type**: `string`
 - **Example**: `boundaries.county_boundaries`

src/explorer/src/pages/getting-started.astro

@@ -82,7 +82,7 @@ import Chrome from '../layouts/Chrome.astro';
                 <h5 class="text-lg font-medium">
                   Make a request<p class="text-base text-slate-500">
                     Use your favorite programming language or an UGRC tool. Maybe the <a
-                      href="https://gis.utah.gov/data/address-geocoders-locators/#OfficialClient"
+                      href="https://gis.utah.gov/products/sgid/address/api-client/"
                       class="text-mustard-900 italic font-medium active:text-mustard-500 focus:outline-none underline underline-offset-2 hover:underline-offset-4 decoration-mustard-500 active:underline-offset-8 active:decoration-mustard-600 hover:decoration-2 transition-all"
                       >API Client</a
                     >?
@@ -133,7 +133,7 @@ import Chrome from '../layouts/Chrome.astro';
         > is a browser based application. The request to the UGRC API is created in javascript running inside the browser
         using the browser's fetch API or with an XHR request. Desktop based applications run on a computer or a server. For
         example, the <a
-          href="https://gis.utah.gov/data/address-geocoders-locators/#OfficialClient"
+          href="https://gis.utah.gov/products/sgid/address/api-client/"
           class="text-mustard-900 italic font-medium active:text-mustard-500 focus:outline-none underline underline-offset-2 hover:underline-offset-4 decoration-mustard-500 active:underline-offset-8 active:decoration-mustard-600 hover:decoration-2 transition-all"
           >API Client</a
         > is running on your desktop. The request to the UGRC API is called directly or indirectly from a server side programming

src/explorer/src/pages/index.astro

@@ -92,7 +92,7 @@ import thumb from '../assets/thumb.svg';
           <h1 class="text-2xl font-light text-wavy-600 col-span-2">What is searching</h1>
           <p class="mt-0 text-lg ml-3">
             Searching allows you to search through more than{' '}
-            <a href="https://gis.utah.gov/sgid" class="font-semibold">1,000,000</a> rows of spatial SGID data. With over
+            <a href="https://gis.utah.gov/documentation/sgid/" class="font-semibold">1,000,000</a> rows of spatial SGID data. With over
             <span class="font-semibold">300</span> layers of real-world data that you can run queries against in the
             SGID, the possibilities can be a little overwhelming. But the searching endpoint really opens up the
             opportunity for serious information gathering. You need a way to sift through all that information and make