Merge branch 'develop' into trunk

Author: nicholasio

docs/documentation/01-Getting Started/headless-config.md

@@ -45,7 +45,7 @@ module.exports = {
 
 ## Splitting client/server config
 
-You can split the config between a client and a server config. This is needed when you're setting up [cache handler](/learn/data-fetching/caching/).
+You can split the config between a client and a server config. This is needed when you're setting up [cache handler](/learn/pages-router/data-fetching/caching/).
 
 Simply create a `headstartwp.config.client.js` and a `headstartwp.config.server.js` file and HeadstartWP will pick them up and inject on the appropriate bundle.
 
@@ -196,9 +196,6 @@ This route would automatically handle the following URLs:
 - /books/genre/genre-name -> filter books by genre
 - /books/genre/genre-name/page/2 -> paginate books filtered by genre
 
-:::caution
-The code snippet above does not implement pre-fetching, which you probably want to. Check out the [pre-fetching docs](/learn/data-fetching/prefetching-data-server) for instructions.
-:::
 
 It is also possible to specify a function for 'customTaxonomies', when doing so the default taxonomies will be passed to the function. This can be used for instance to enable archive path matching.
 

docs/versioned_docs/version-pages-router/01-Getting Started/headless-config.md

@@ -45,7 +45,7 @@ module.exports = {
 
 ## Splitting client/server config
 
-You can split the config between a client and a server config. This is needed when you're setting up [cache handler](/learn/data-fetching/caching/).
+You can split the config between a client and a server config. This is needed when you're setting up [cache handler](/learn/pages-router/data-fetching/caching/).
 
 Simply create a `headstartwp.config.client.js` and a `headstartwp.config.server.js` file and HeadstartWP will pick them up and inject on the appropriate bundle.
 
@@ -96,9 +96,9 @@ usePosts({ postType:'book', perPage: 10 });
 
 The `single` option is required for several things including:
 - properly previewing custom post types when the "single" route is at a different prefix. E.g: `/book/da-vince-code` instead of `/da-vice-code`; In this case, the framework will use the `single` path to redirect the previewed post to the right path/route.
-- Matching post path permalinks with the current URL. E.g: when fetching a single custom post type the framework will filter the returned posts to the one that matches the existing URL. Therefore, the framework needs to know the single prefix url for custom post types. This is required to properly handle parent pages that share the same child slug. See [post path mapping](/learn/data-fetching/usepost/#post-path-matching) for more info.
+- Matching post path permalinks with the current URL. E.g: when fetching a single custom post type the framework will filter the returned posts to the one that matches the existing URL. Therefore, the framework needs to know the single prefix url for custom post types. This is required to properly handle parent pages that share the same child slug. See [post path mapping](/learn/pages-router/data-fetching/usepost/#post-path-matching) for more info.
 
-It is also possible to pass a function, when doing so the default post types (post and pages) will be passed to the function. The code snipped below will disable [post path mapping](/learn/data-fetching/usepost/#post-path-matching) to the default post types.
+It is also possible to pass a function, when doing so the default post types (post and pages) will be passed to the function. The code snipped below will disable [post path mapping](/learn/pages-router/data-fetching/usepost/#post-path-matching) to the default post types.
 
 ```js title="headstartwp.config.js"
 module.exports = {
@@ -201,10 +201,10 @@ This route would automatically handle the following URLs:
 - /books/genre/genre-name/page/2 -> paginate books filtered by genre
 
 :::caution
-The code snippet above does not implement pre-fetching, which you probably want to. Check out the [pre-fetching docs](/learn/data-fetching/prefetching) for instructions.
+The code snippet above does not implement pre-fetching, which you probably want to. Check out the [pre-fetching docs](/learn/pages-router/data-fetching/prefetching) for instructions.
 :::
 
-It is also possible to specify a function for 'customTaxonomies', when doing so the default taxonomies will be passed to the function. This can be used for instance to enable [archive path matching](/learn/data-fetching/useposts#archive-path-matching).
+It is also possible to specify a function for 'customTaxonomies', when doing so the default taxonomies will be passed to the function. This can be used for instance to enable [archive path matching](/learn/pages-router/data-fetching/useposts#archive-path-matching).
 
 ```js title="headstartwp.config.js"
 module.exports = {
@@ -281,8 +281,8 @@ module.exports = {
 }
 ```
 
-More for info check out the [preview docs](/learn/wordpress-integration/previews#the-usepostlinkforredirect-setting).
+More for info check out the [preview docs](/learn/pages-router/wordpress-integration/previews#the-usepostlinkforredirect-setting).
 
 ## cache
 
-See [caching](/learn/data-fetching/caching/) docs.
+See [caching](/learn/pages-router/data-fetching/caching/) docs.

docs/versioned_docs/version-pages-router/02-Data Fetching/usePost.md

@@ -67,7 +67,7 @@ Example where path does not match but is redirected to the right one:
 - User visits URL `/post-name`
 - The post with the `post-name` slug contains a `http://backend.com/2022/10/30/post-name` url
 - Since the URL and the path of `post.link` do not match, a NotFound error is thrown
-- If prefetching is setup following [pre-fetching](/learn/data-fetching/prefetching) and `redirectStrategy` is set to "404" or "always" in `headstartwp.config.js`, `handleError` will then look if there's a redirect available and since WordPress redirects `/post-name` to `/2022/10/30/post-name`, the framework will also perform the redirect.
+- If prefetching is setup following [pre-fetching](/learn/pages-router/data-fetching/prefetching) and `redirectStrategy` is set to "404" or "always" in `headstartwp.config.js`, `handleError` will then look if there's a redirect available and since WordPress redirects `/post-name` to `/2022/10/30/post-name`, the framework will also perform the redirect.
 
 
 ### Fetching from multiple post types

docs/versioned_docs/version-pages-router/02-Data Fetching/useSearch.md

@@ -48,7 +48,7 @@ The route will automatically render the latest 10 posts if no search term is pro
 
 ## QueriedObject
 
-The `useSearch` hook also exposes a `queriedObject`. See [usePosts docs](/learn/data-fetching/useposts/#queried-object) for more info.
+The `useSearch` hook also exposes a `queriedObject`. See [usePosts docs](/learn/pages-router/data-fetching/useposts/#queried-object) for more info.
 
 The queried object for for this hook is an object of type [SearchEntity](/api/interfaces/headstartwp_core.SearchEntity/).
 

docs/versioned_docs/version-pages-router/02-Data Fetching/useTerms.md

@@ -18,5 +18,5 @@ const {
 ```
 
 :::caution
-You do not need to use `useTerms` if you simply need to access the term object for a taxonomy archive page (e.g category archive). You should use the `queriedObject` from the `usePosts` hook. See [usePosts docs](/learn/data-fetching/useposts/#queried-object) for more details.
+You do not need to use `useTerms` if you simply need to access the term object for a taxonomy archive page (e.g category archive). You should use the `queriedObject` from the `usePosts` hook. See [usePosts docs](/learn/pages-router/data-fetching/useposts/#queried-object) for more details.
 :::

docs/versioned_docs/version-pages-router/08-Guides/linaria.md

@@ -6,7 +6,7 @@ HeadstartWP offers a straightforward integration with [Linaria](https://github.c
 npm install --save-dev @linaria/babel-preset @linaria/core @linaria/react @linaria/shaker @linaria/webpack-loader
 ```
 
-The [withHeadstartWPConfig](/docs/api/namespaces/headstartwp_next.config/#withheadstartwpconfig) function will detect the presence of the Linaria packages and will enable the build steps necessary to compile Linaria.
+The [withHeadstartWPConfig](/api/namespaces/headstartwp_next.config/#withheadstartwpconfig) function will detect the presence of the Linaria packages and will enable the build steps necessary to compile Linaria.
 
 :::caution
 If you're on a monorepo setup, these packages should be installed on the Next.js project.