Moved v3 ref out of main index.md

kasperbolarsen · Jun 23, 2024 · 0368bb3 · 0368bb3
1 parent 0f43d3c
commit 0368bb3
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 13 deletions.
diff --git a/docs/index.md b/docs/index.md
@@ -1,4 +1,4 @@
-!["PnP"](./assets/pnp_logo.png){: .center .logo}
+!["PnP"](./assets/pnp_logo.png){: .center .logo } 
 
 # PnP Modern Search v4
 
@@ -18,18 +18,6 @@ Hence v4 was born. The goal of v4 is to solve scenarios already solved by v3, bu
 
 As more and more Microsoft Search functionality is exposed via the Microsoft Graph Search API's, we will keep on investing in v4 to surface these great capabilities.
 
-**Looking for the v3 documentation? [Here you go!](./v3/index.md)**
-
-!!! important "PnP Modern Search v3.x deprecation"
-    **v4 uses a brand new code architecture and replace the older v3 codebase**. There will be no new features added to v3.x, but we will continue to
-    provide bug fixes and minor changes as needed. As v4.x is not yet at feature parity with v3.x, you can still use the v3.x packages to meet your requirements.
-    Also not that there is not an auto-upgrade path from v3 to v4 due to the new architecture, so you are perfectly ok
-    to stay on the v3 version until v4 provides the features validating your upgrade.
-    However, the main focus is on the v4 version, and new search functionality backed by the Microsoft Graph Search API will be v4 only.
-
-    **v3 and v4 don't share the same package name, Web Part and solution IDs meaning you can have them side by side on a page if necessary without overlap.**
-
-    !["V3 & v4"](./assets/v3_v4.png){: .center}
 
 ## What's included?
 

diff --git a/docs/v3/index.md b/docs/v3/index.md
@@ -1,5 +1,16 @@
 # PnP Modern Search v3 #
 
+!!! important "PnP Modern Search v3.x deprecation"
+    **v4 uses a brand new code architecture and replace the older v3 codebase**. There will be no new features added to v3.x, but we will continue to
+    provide bug fixes and minor changes as needed. As v4.x is not yet at feature parity with v3.x, you can still use the v3.x packages to meet your requirements.
+    Also not that there is not an auto-upgrade path from v3 to v4 due to the new architecture, so you are perfectly ok
+    to stay on the v3 version until v4 provides the features validating your upgrade.
+    However, the main focus is on the v4 version, and new search functionality backed by the Microsoft Graph Search API will be v4 only.
+
+    **v3 and v4 don't share the same package name, Web Part and solution IDs meaning you can have them side by side on a page if necessary without overlap.**
+
+    !["V3 & v4"](./assets/v3_v4.png){: .center}
+
 ## Solution overview
 
 ![Solution demo](./images/react-search-refiners.gif)

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -9,6 +9,7 @@ nav:
     - Create custom layouts: create-custom-layouts/index.md
     - How to contribute?: how-to-contribute.md 
     - Building documentation: build-the-doc.md
+    - Version 3 : v3/index.md
   - Search Results:
     - Usage: usage/search-results/index.md
     - Data sources: usage/search-results/data-sources/index.md