docs: Prepare for new sub tree

See #11925

docs/content/en/functions/global/_index.md

@@ -1,11 +0,0 @@
----
-title: Global functions
-linkTitle: global
-description: Global template functions to access page and site data.
-categories: []
-menu:
-  docs:
-    parent: functions
----
-
-Use these global functions to access page and site data.

docs/content/en/functions/global/page.md

@@ -1,109 +0,0 @@
----
-title: page
-description: Provides global access to a Page object.
-categories: []
-keywords: []
-action:
-  aliases: []
-  related:
-    - functions/global/site
-  returnType: 
-  signatures: [page]
-toc: true
-aliases: [/functions/page]
----
-
-{{< new-in 0.111.0 >}}
-
-At the top level of a template that receives a `Page` object in context, these are equivalent:
-
-```go-html-template
-{{ .Params.foo }}
-{{ .Page.Params.foo }}
-{{ page.Params.foo }}
-```
-
-When a `Page` object is not in context, you can use the global `page` function:
-
-```go-html-template
-{{ page.Params.foo }}
-```
-
-{{% note %}}
-Do not use the global `page` function in shortcodes, partials called by shortcodes, or cached partials. See [warnings](#warnings) below.
-{{% /note %}}
-
-## Explanation
-
-Hugo almost always passes a `Page` as the data context into the top level template (e.g., `single.html`). The one exception is the multihost sitemap template. This means that you can access the current page with the `.` variable in the template.
-
-But when you are deeply nested inside of a [content view], [partial], or [render hook], it is not always practical or possible to access the `Page` object.
-
-Use the global `page` function to access the `Page` object from anywhere in any template.
-
-## Warnings
-
-### Be aware of top-level context
-
-The global `page` function accesses the `Page` object passed into the top-level template.
-
-With this content structure:
-
-```text
-content/
-├── posts/
-│   ├── post-1.md
-│   ├── post-2.md
-│   └── post-3.md
-└── _index.md      <-- title is "My Home Page"
-```
-
-And this code in the home page template:
-
-```go-html-template
-{{ range site.Sections }}
-  {{ range .Pages }}
-    {{ page.Title }}
-  {{ end }}
-{{ end }}
-```
-
-The rendered output will be:
-
-```text
-My Home Page
-My Home Page
-My Home Page
-```
-
-In the example above, the global `page` function accesses the `Page` object passed into the home page template; it does not access the `Page` object of the iterated pages.
-
-### Be aware of caching
-
-Do not use the global `page` function in:
-
-- Shortcodes
-- Partials called by shortcodes
-- Partials cached by the [`partialCached`] function
-
-Hugo caches rendered shortcodes. If you use the global `page` function within a shortcode, and the page content is rendered in two or more templates, the cached shortcode may be incorrect.
-
-Consider this section template:
-
-```go-html-template
-{{ range .Pages }}
-  <h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2>
-  {{ .Summary }}
-{{ end }}
-```
-
-When you call the [`Summary`] method, Hugo renders the page content including shortcodes. In this case, within a shortcode, the global `page` function accesses the `Page` object of the section page, not the content page.
-
-If Hugo renders the section page before a content page, the cached rendered shortcode will be incorrect. You cannot control the rendering sequence due to concurrency.
-
-[`Summary`]: /methods/page/summary
-[`partialCached`]: /functions/partials/includecached
-[content view]: /getting-started/glossary/#content-view
-[partial]: /getting-started/glossary/#partial
-[render hook]: /getting-started/glossary/#render-hook
-[shortcode]: getting-started/glossary/#shortcode

docs/content/en/functions/global/site.md

@@ -1,30 +0,0 @@
----
-title: site
-description: Provides global access to the current Site object.
-categories: []
-keywords: []
-action:
-  aliases: []
-  related:
-    - functions/global/page
-  returnType: 
-  signatures: [site]
-aliases: [/functions/site]
----
-
-At the top level of a template that receives the `Site` object in context, these are equivalent:
-
-```go-html-template
-{{ .Site.Params.foo }}
-{{ site.Params.foo }}
-```
-
-When the `Site` object is not in context, use the global `site` function:
-
-```go-html-template
-{{ site.Params.foo }}
-```
-
-{{% note %}}
-To simplify your templates, use the global `site` function regardless of whether the `Site` object is in context.
-{{% /note %}}