espiat · May 12, 2025 04:29 · May 10, 2025 · May 10, 2025 · May 10, 2025 · May 10, 2025
diff --git a/wp-articles.md b/wp-articles.md
diff --git a/wp-adv-admin-handbook.md b/wp-adv-admin-handbook.md
diff --git a/wp-apis-handbook.md b/wp-apis-handbook.md
diff --git a/wp-blocks-handbook.md b/wp-blocks-handbook.md
diff --git a/wp-handbooks.md b/wp-handbooks.md
diff --git a/wp-plugin-handbook.md b/wp-plugin-handbook.md
diff --git a/wp-rest-api-handbook.md b/wp-rest-api-handbook.md
diff --git a/wp-scf-handbook.md b/wp-scf-handbook.md
@@ -1,4 +1,4 @@
-# Core Concepts
+# Core Concepts <a id="secure-custom-fields/concepts" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/concepts/
 
@@ -15,7 +15,7 @@ Secure Custom Fields is built on several core concepts that ensure security, fle
 
 ---
 
-# Architecture
+# Architecture <a id="secure-custom-fields/concepts/architecture" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/concepts/architecture/
 
@@ -125,7 +125,7 @@ The plugin is organized into several key directories:
 
 ---
 
-# Security in Secure Custom Fields
+# Security in Secure Custom Fields <a id="secure-custom-fields/concepts/security" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/concepts/security/
 
@@ -157,7 +157,7 @@ When working with SCF:
 
 ---
 
-# Contributing to SCF
+# Contributing to SCF <a id="secure-custom-fields/contributing" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/contributing/
 
@@ -201,7 +201,7 @@ Guide for contributing to Secure Custom Fields development.
 
 ---
 
-# Documentation Guidelines
+# Documentation Guidelines <a id="secure-custom-fields/contributing/documentation" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/contributing/documentation/
 
@@ -242,7 +242,7 @@ We follow the [WordPress Documentation Style Guide](https://make.wordpress.org/d
 
 ---
 
-# Features
+# Features <a id="secure-custom-fields/features" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/
 
@@ -298,7 +298,7 @@ This section details all features available in Secure Custom Fields.
 
 ---
 
-# Api
+# Api <a id="secure-custom-fields/code-reference/api" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/api/
 
@@ -310,7 +310,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/api/
 
 ---
 
-# Custom Post Types
+# Custom Post Types <a id="secure-custom-fields/features/post-types" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/post-types/
 
@@ -354,7 +354,7 @@ Common use cases for custom post types:
 
 ---
 
-# Installing Secure Custom Fields
+# Installing Secure Custom Fields <a id="secure-custom-fields/welcome/installation" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/welcome/installation/
 
@@ -395,7 +395,7 @@ After installation:
 
 ---
 
-# Quick Start Guide
+# Quick Start Guide <a id="secure-custom-fields/welcome/quick-start" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/welcome/quick-start/
 
@@ -431,7 +431,7 @@ Let’s create a simple author bio field group:
 
 ---
 
-# Tutorials
+# Tutorials <a id="secure-custom-fields/tutorials" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/tutorials/
 
@@ -461,7 +461,7 @@ Each tutorial follows these principles:
 
 ---
 
-# Creating Your First Post Type
+# Creating Your First Post Type <a id="secure-custom-fields/tutorials/first-post-type" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/tutorials/first-post-type/
 
@@ -499,7 +499,7 @@ A step-by-step guide to creating a custom post type using Secure Custom Fields.
 
 ---
 
-# Fields
+# Fields <a id="secure-custom-fields/code-reference/fields" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/
 
@@ -509,7 +509,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Accordion Field
+# Accordion Field <a id="secure-custom-fields/code-reference/fields/accordion" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/accordion/
 
@@ -530,7 +530,7 @@ The Accordion field creates collapsible sections to organize your fields into lo
 
 ---
 
-# Using the Accordion Field
+# Using the Accordion Field <a id="secure-custom-fields/code-reference/fields/accordion/accordion-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/accordion/accordion-tutorial/
 
@@ -563,7 +563,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Button Group Field
+# Button Group Field <a id="secure-custom-fields/code-reference/fields/button-group" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/button-group/
 
@@ -585,7 +585,7 @@ The Button Group field provides a set of buttons where users can select one opti
 
 ---
 
-# Using the Button Group Field
+# Using the Button Group Field <a id="secure-custom-fields/code-reference/fields/button-group/button-group-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/button-group/button-group-tutorial/
 
@@ -618,7 +618,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Checkbox Field
+# Checkbox Field <a id="secure-custom-fields/code-reference/fields/checkbox" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/checkbox/
 
@@ -641,7 +641,7 @@ The Checkbox field allows users to select one or multiple choices from a set of
 
 ---
 
-# Using the Checkbox Field
+# Using the Checkbox Field <a id="secure-custom-fields/code-reference/fields/checkbox/checkbox-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/checkbox/checkbox-tutorial/
 
@@ -675,7 +675,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Clone Field
+# Clone Field <a id="secure-custom-fields/code-reference/fields/clone" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/clone/
 
@@ -697,7 +697,7 @@ The Clone field allows you to reuse existing fields or field groups in multiple
 
 ---
 
-# Using the Clone Field
+# Using the Clone Field <a id="secure-custom-fields/code-reference/fields/clone/clone-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/clone/clone-tutorial/
 
@@ -731,7 +731,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Color Picker Field
+# Color Picker Field <a id="secure-custom-fields/code-reference/fields/color-picker" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/color-picker/
 
@@ -753,7 +753,7 @@ The Color Picker field provides an interactive interface for selecting colors. I
 
 ---
 
-# Using the Color Picker Field
+# Using the Color Picker Field <a id="secure-custom-fields/code-reference/fields/color-picker/color-picker-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/color-picker/color-picker-tutorial/
 
@@ -787,7 +787,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Date Picker Field
+# Date Picker Field <a id="secure-custom-fields/code-reference/fields/date-picker" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/date-picker/
 
@@ -810,7 +810,7 @@ The Date Picker field provides a calendar interface for selecting dates. It offe
 
 ---
 
-# Using the Date Picker Field
+# Using the Date Picker Field <a id="secure-custom-fields/code-reference/fields/date-picker/date-picker-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/date-picker/date-picker-tutorial/
 
@@ -844,7 +844,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Date Time Picker Field
+# Date Time Picker Field <a id="secure-custom-fields/code-reference/fields/date-time-picker" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/date-time-picker/
 
@@ -867,7 +867,7 @@ The Date Time Picker field combines date and time selection into a single interf
 
 ---
 
-# Using the Date Time Picker Field
+# Using the Date Time Picker Field <a id="secure-custom-fields/code-reference/fields/date-time-picker/date-time-picker-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/date-time-picker/date-time-picker-tutorial/
 
@@ -901,7 +901,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Email Field
+# Email Field <a id="secure-custom-fields/code-reference/fields/email" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/email/
 
@@ -924,7 +924,7 @@ The Email field provides a specialized input for email addresses. It includes bu
 
 ---
 
-# Using the Email Field
+# Using the Email Field <a id="secure-custom-fields/code-reference/fields/email/email-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/email/email-tutorial/
 
@@ -958,7 +958,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# File Field
+# File Field <a id="secure-custom-fields/code-reference/fields/file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/file/
 
@@ -982,7 +982,7 @@ The File field enables file uploads and management through the WordPress media l
 
 ---
 
-# Using the File Field
+# Using the File Field <a id="secure-custom-fields/code-reference/fields/file/file-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/file/file-tutorial/
 
@@ -1016,7 +1016,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Flexible Content Field
+# Flexible Content Field <a id="secure-custom-fields/code-reference/fields/flexible-content" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/flexible-content/
 
@@ -1039,7 +1039,7 @@ The Flexible Content field provides a flexible content builder interface. It all
 
 ---
 
-# Using the Flexible Content Field
+# Using the Flexible Content Field <a id="secure-custom-fields/code-reference/fields/flexible-content/flexible-content-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/flexible-content/flexible-content-tutorial/
 
@@ -1073,7 +1073,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Gallery Field
+# Gallery Field <a id="secure-custom-fields/code-reference/fields/gallery" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/gallery/
 
@@ -1097,7 +1097,7 @@ The Gallery field enables management of multiple images in a single field. It pr
 
 ---
 
-# Using the Gallery Field
+# Using the Gallery Field <a id="secure-custom-fields/code-reference/fields/gallery/gallery-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/gallery/gallery-tutorial/
 
@@ -1131,7 +1131,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Google Map Field
+# Google Map Field <a id="secure-custom-fields/code-reference/fields/google-map" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/google-map/
 
@@ -1155,7 +1155,7 @@ The Google Map field provides an interactive map interface for selecting and sto
 
 ---
 
-# Using the Google Map Field
+# Using the Google Map Field <a id="secure-custom-fields/code-reference/fields/google-map/google-map-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/google-map/google-map-tutorial/
 
@@ -1189,7 +1189,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Group Field
+# Group Field <a id="secure-custom-fields/code-reference/fields/group" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/group/
 
@@ -1211,7 +1211,7 @@ The Group field allows you to organize multiple fields together into a single da
 
 ---
 
-# Using the Group Field
+# Using the Group Field <a id="secure-custom-fields/code-reference/fields/group/group-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/group/group-tutorial/
 
@@ -1245,7 +1245,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Icon Picker Field
+# Icon Picker Field <a id="secure-custom-fields/code-reference/fields/icon-picker" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/icon-picker/
 
@@ -1268,7 +1268,7 @@ The Icon Picker field provides an interface for selecting icons from various sou
 
 ---
 
-# Using the Icon Picker Field
+# Using the Icon Picker Field <a id="secure-custom-fields/code-reference/fields/icon-picker/icon-picker-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/icon-picker/icon-picker-tutorial/
 
@@ -1302,7 +1302,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Image Field
+# Image Field <a id="secure-custom-fields/code-reference/fields/image" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/image/
 
@@ -1326,7 +1326,7 @@ The Image field provides a dedicated interface for uploading and selecting image
 
 ---
 
-# Using the Image Field
+# Using the Image Field <a id="secure-custom-fields/code-reference/fields/image/image-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/image/image-tutorial/
 
@@ -1360,7 +1360,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Link Field
+# Link Field <a id="secure-custom-fields/code-reference/fields/link" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/link/
 
@@ -1382,7 +1382,7 @@ The Link field provides an interface for creating links with various properties.
 
 ---
 
-# Using the Link Field
+# Using the Link Field <a id="secure-custom-fields/code-reference/fields/link/link-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/link/link-tutorial/
 
@@ -1416,7 +1416,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Message Field
+# Message Field <a id="secure-custom-fields/code-reference/fields/message" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/message/
 
@@ -1439,7 +1439,7 @@ The Message field displays instructional text or HTML content within the editing
 
 ---
 
-# Using the Message Field
+# Using the Message Field <a id="secure-custom-fields/code-reference/fields/message/message-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/message/message-tutorial/
 
@@ -1473,7 +1473,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Number Field
+# Number Field <a id="secure-custom-fields/code-reference/fields/number" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/number/
 
@@ -1499,7 +1499,7 @@ The Number field provides an input specifically for numeric values. It includes
 
 ---
 
-# Using the Number Field
+# Using the Number Field <a id="secure-custom-fields/code-reference/fields/number/number-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/number/number-tutorial/
 
@@ -1533,7 +1533,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# oEmbed Field
+# oEmbed Field <a id="secure-custom-fields/code-reference/fields/oembed" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/oembed/
 
@@ -1555,7 +1555,7 @@ The oEmbed field allows embedding external content from various providers like Y
 
 ---
 
-# Using the oEmbed Field
+# Using the oEmbed Field <a id="secure-custom-fields/code-reference/fields/oembed/oembed-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/oembed/oembed-tutorial/
 
@@ -1589,7 +1589,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Page Link Field
+# Page Link Field <a id="secure-custom-fields/code-reference/fields/page-link" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/page-link/
 
@@ -1613,7 +1613,7 @@ The Page Link field provides an interface for creating links to internal WordPre
 
 ---
 
-# Using the Page Link Field
+# Using the Page Link Field <a id="secure-custom-fields/code-reference/fields/page-link/page-link-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/page-link/page-link-tutorial/
 
@@ -1647,7 +1647,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Password Field
+# Password Field <a id="secure-custom-fields/code-reference/fields/password" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/password/
 
@@ -1669,7 +1669,7 @@ The Password field provides a secure input for password data. It includes maskin
 
 ---
 
-# Using the Password Field
+# Using the Password Field <a id="secure-custom-fields/code-reference/fields/password/password-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/password/password-tutorial/
 
@@ -1703,7 +1703,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Post Object Field
+# Post Object Field <a id="secure-custom-fields/code-reference/fields/post-object" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/post-object/
 
@@ -1727,7 +1727,7 @@ The Post Object field creates relationships with other WordPress posts, pages, o
 
 ---
 
-# Using the Post Object Field
+# Using the Post Object Field <a id="secure-custom-fields/code-reference/fields/post-object/post-object-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/post-object/post-object-tutorial/
 
@@ -1761,7 +1761,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Radio Field
+# Radio Field <a id="secure-custom-fields/code-reference/fields/radio" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/radio/
 
@@ -1785,7 +1785,7 @@ The Radio field presents users with a list of options where they can select a si
 
 ---
 
-# Using the Radio Field
+# Using the Radio Field <a id="secure-custom-fields/code-reference/fields/radio/radio-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/radio/radio-tutorial/
 
@@ -1819,7 +1819,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Range Field
+# Range Field <a id="secure-custom-fields/code-reference/fields/range" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/range/
 
@@ -1843,7 +1843,7 @@ The Range field provides a slider interface for selecting numeric values within
 
 ---
 
-# Using the Range Field
+# Using the Range Field <a id="secure-custom-fields/code-reference/fields/range/range-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/range/range-tutorial/
 
@@ -1877,7 +1877,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fiel
 
 ---
 
-# Code Reference
+# Code Reference <a id="secure-custom-fields/code-reference" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/
 
@@ -1917,7 +1917,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/
 
 ---
 
-# Acf Bidirectional Functions Global Functions
+# Acf Bidirectional Functions Global Functions <a id="secure-custom-fields/code-reference/acf-bidirectional-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-bidirectional-functions-file/
 
@@ -1974,7 +1974,7 @@ Returns the translated instructional text for the message field for the bidirect
 
 ---
 
-# Acf Field Functions Global Functions
+# Acf Field Functions Global Functions <a id="secure-custom-fields/code-reference/acf-field-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-field-functions-file/
 
@@ -2002,7 +2002,7 @@ acf\_get\_raw\_field
 
 acf\_get\_field\_post
 
-- Retrieves the field’s [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/) object.
+- Retrieves the field’s [WP\_Post](#reference/classes/wp_post) object.
 - @date 18/1/19
 - @since ACF 5.7.10
 - @param (int|string) $id The field ID, key or name.
@@ -2373,7 +2373,7 @@ acf\_prepare\_field\_for\_import
 
 ---
 
-# Acf Field Group Functions Global Functions
+# Acf Field Group Functions Global Functions <a id="secure-custom-fields/code-reference/acf-field-group-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-field-group-functions-file/
 
@@ -2401,7 +2401,7 @@ acf\_get\_raw\_field\_group
 
 acf\_get\_field\_group\_post
 
-- Retrieves the field group’s [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/) object.
+- Retrieves the field group’s [WP\_Post](#reference/classes/wp_post) object.
 - @date 18/1/19
 - @since ACF 5.7.10
 - @param (int|string) $id The field group’s ID, key or name.
@@ -2665,7 +2665,7 @@ Checks if a field group has the provided location rule.
 
 ---
 
-# Acf Form Functions Global Functions
+# Acf Form Functions Global Functions <a id="secure-custom-fields/code-reference/acf-form-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-form-functions-file/
 
@@ -2725,7 +2725,7 @@ acf\_save\_post
 
 ---
 
-# Acf Helper Functions Global Functions
+# Acf Helper Functions Global Functions <a id="secure-custom-fields/code-reference/acf-helper-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-helper-functions-file/
 
@@ -2948,7 +2948,7 @@ Returns the length of a string that has been submitted via $\_POST.
 - Uses the following process:
 
 1. Unslash the string because posted values will be slashed.
-2. Decode special characters because [wp\_kses()](https://developer.wordpress.org/reference/functions/wp_kses/) will normalize entities.
+2. Decode special characters because [wp\_kses()](#reference/functions/wp_kses) will normalize entities.
 3. Treat line-breaks as a single character instead of two.
 4. Use mb\_strlen() to accommodate special characters.
 
@@ -3037,7 +3037,7 @@ this function returns false (boolean) to indicate that the version could not be
 
 ---
 
-# Acf Hook Functions Global Functions
+# Acf Hook Functions Global Functions <a id="secure-custom-fields/code-reference/acf-hook-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-hook-functions-file/
 
@@ -3069,7 +3069,7 @@ acf\_add\_action\_variations
 
 \_acf\_apply\_hook\_variations
 
-- Applies hook variations during [apply\_filters()](https://developer.wordpress.org/reference/functions/apply_filters/) or [do\_action()](https://developer.wordpress.org/reference/functions/do_action/) .
+- Applies hook variations during [apply\_filters()](#reference/functions/apply_filters) or [do\_action()](#reference/functions/do_action) .
 - @date 25/1/19
 - @since ACF 5.7.11
 - @param mixed
@@ -3101,7 +3101,7 @@ acf\_add\_deprecated\_action
 
 ## `_acf_apply_deprecated_hook()`
 
-Applies a deprecated filter during [apply\_filters()](https://developer.wordpress.org/reference/functions/apply_filters/) or [do\_action()](https://developer.wordpress.org/reference/functions/do_action/) .
+Applies a deprecated filter during [apply\_filters()](#reference/functions/apply_filters) or [do\_action()](#reference/functions/do_action) .
 
 - @date 25/1/19
 - @since ACF 5.7.11
@@ -3112,7 +3112,7 @@ Applies a deprecated filter during [apply\_filters()](https://developer.wordpres
 
 ---
 
-# Acf Input Functions Global Functions
+# Acf Input Functions Global Functions <a id="secure-custom-fields/code-reference/acf-input-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-input-functions-file/
 
@@ -3361,7 +3361,7 @@ acf\_esc\_atts\_e
 
 ---
 
-# Acf Internal Post Type Functions Global Functions
+# Acf Internal Post Type Functions Global Functions <a id="secure-custom-fields/code-reference/acf-internal-post-type-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-internal-post-type-functions-file/
 
@@ -3668,7 +3668,7 @@ Gets an ACF options page from request args and verifies nonce based on action.
 
 ---
 
-# Acf Meta Functions Global Functions
+# Acf Meta Functions Global Functions <a id="secure-custom-fields/code-reference/acf-meta-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-meta-functions-file/
 
@@ -3685,7 +3685,7 @@ Returns an array of “ACF only” meta for the given post\_id.
 
 acf\_get\_option\_meta
 
-- Returns an array of meta for the given wp\_option name prefix in the same format as [get\_post\_meta()](https://developer.wordpress.org/reference/functions/get_post_meta/) .
+- Returns an array of meta for the given wp\_option name prefix in the same format as [get\_post\_meta()](#reference/functions/get_post_meta) .
 - @date 9/10/18
 - @since ACF 5.8.0
 - @param string $prefix The wp\_option name prefix.
@@ -3788,7 +3788,7 @@ acf\_update\_metaref
 
 ---
 
-# Acf Post Functions Global Functions
+# Acf Post Functions Global Functions <a id="secure-custom-fields/code-reference/acf-post-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-post-functions-file/
 
@@ -3804,7 +3804,7 @@ Returns available templates for each post type.
 
 ---
 
-# Acf Post Type Functions Global Functions
+# Acf Post Type Functions Global Functions <a id="secure-custom-fields/code-reference/acf-post-type-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-post-type-functions-file/
 
@@ -3996,7 +3996,7 @@ Exports the “Enter Title Here” text for the provided ACF post types.
 
 ---
 
-# Acf Taxonomy Functions Global Functions
+# Acf Taxonomy Functions Global Functions <a id="secure-custom-fields/code-reference/acf-taxonomy-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-taxonomy-functions-file/
 
@@ -4180,15 +4180,15 @@ Imports an ACF taxonomy into the database.
 
 ---
 
-# Acf User Functions Global Functions
+# Acf User Functions Global Functions <a id="secure-custom-fields/code-reference/acf-user-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-user-functions-file/
 
 ## `acf_get_users()`
 
 acf\_get\_users
 
-- Similar to the [get\_users()](https://developer.wordpress.org/reference/functions/get_users/) function but with extra functionality.
+- Similar to the [get\_users()](#reference/functions/get_users) function but with extra functionality.
 - @date 9/1/19
 - @since ACF 5.7.10
 - @param array $args The query args.
@@ -4201,7 +4201,7 @@ acf\_get\_user\_result
 - Returns a result containing “id” and “text” for the given user.
 - @date 21/5/19
 - @since ACF 5.8.1
-- @param [WP\_User](https://developer.wordpress.org/reference/classes/wp_user/) $user The user object.
+- @param [WP\_User](#reference/classes/wp_user) $user The user object.
 - @return array
 
 ## `acf_get_user_role_labels()`
@@ -4227,7 +4227,7 @@ acf\_allow\_unfiltered\_html
 
 ---
 
-# Acf Utility Functions Global Functions
+# Acf Utility Functions Global Functions <a id="secure-custom-fields/code-reference/acf-utility-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-utility-functions-file/
 
@@ -4316,7 +4316,7 @@ Includes a file within the ACF plugin.
 
 ---
 
-# Acf Value Functions Global Functions
+# Acf Value Functions Global Functions <a id="secure-custom-fields/code-reference/acf-value-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-value-functions-file/
 
@@ -4421,7 +4421,7 @@ Potentially log an error if a field doesn’t exist when we expect it to.
 
 ---
 
-# Acf Wp Functions Global Functions
+# Acf Wp Functions Global Functions <a id="secure-custom-fields/code-reference/acf-wp-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/acf-wp-functions-file/
 
@@ -4447,25 +4447,25 @@ Decodes a post\_id value such as 1 or “user\_1” into an array containing the
 ## `acf_get_object_type_rest_base()`
 
 Determine the REST base for a post type or taxonomy object. Note that this is not intended for use  
-with term or post objects but is, instead, to be used with the underlying [WP\_Post\_Type](https://developer.wordpress.org/reference/classes/wp_post_type/) and [WP\_Taxonomy](https://developer.wordpress.org/reference/classes/wp_taxonomy/)  
+with term or post objects but is, instead, to be used with the underlying [WP\_Post\_Type](#reference/classes/wp_post_type) and [WP\_Taxonomy](#reference/classes/wp_taxonomy)  
 instances.
 
-- @param [WP\_Post\_Type](https://developer.wordpress.org/reference/classes/wp_post_type/)|[WP\_Taxonomy](https://developer.wordpress.org/reference/classes/wp_taxonomy/) $type\_object
+- @param [WP\_Post\_Type](#reference/classes/wp_post_type)|[WP\_Taxonomy](#reference/classes/wp_taxonomy) $type\_object
 - @return string|null
 
 ## `acf_get_object_id()`
 
 Extract the ID of a given object/array. This supports all expected types handled by our update\_fields() and  
 load\_fields() callbacks.
 
-- @param [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/)|[WP\_User](https://developer.wordpress.org/reference/classes/wp_user/)|[WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/)|[WP\_Comment](https://developer.wordpress.org/reference/classes/wp_comment/)|array $object
+- @param [WP\_Post](#reference/classes/wp_post)|[WP\_User](#reference/classes/wp_user)|[WP\_Term](#reference/classes/wp_term)|[WP\_Comment](#reference/classes/wp_comment)|array $object
 - @return integer|mixed|null
 
 ---
 
 ---
 
-# Assets Global Functions
+# Assets Global Functions <a id="secure-custom-fields/code-reference/assets-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/assets-file/
 
@@ -4517,7 +4517,7 @@ Enqueues the WP media uploader scripts and styles.
 
 ---
 
-# Blocks Global Functions
+# Blocks Global Functions <a id="secure-custom-fields/code-reference/blocks-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/blocks-file/
 
@@ -4643,7 +4643,7 @@ The render callback for all ACF blocks.
 - @since ACF 5.9.2
 - @param array $attributes The block attributes.
 - @param string $content The block content.
-- @param [WP\_Block](https://developer.wordpress.org/reference/classes/wp_block/) $wp\_block The block instance (since WP 5.5).
+- @param [WP\_Block](#reference/classes/wp_block) $wp\_block The block instance (since WP 5.5).
 - @return string The block HTML.
 
 ## `acf_rendered_block()`
@@ -4656,7 +4656,7 @@ Returns the rendered block HTML.
 - @param string $content The block content.
 - @param boolean $is\_preview Whether or not the block is being rendered for editing preview.
 - @param integer $post\_id The current post being edited or viewed.
-- @param [WP\_Block](https://developer.wordpress.org/reference/classes/wp_block/) $wp\_block The block instance (since WP 5.5).
+- @param [WP\_Block](#reference/classes/wp_block) $wp\_block The block instance (since WP 5.5).
 - @param array $context The block context array.
 - @param boolean $is\_ajax\_render Whether or not this is an ACF AJAX render.
 - @return string The block HTML.
@@ -4670,7 +4670,7 @@ Renders the block HTML.
 - @param string $content The block content.
 - @param boolean $is\_preview Whether or not the block is being rendered for editing preview.
 - @param integer $post\_id The current post being edited or viewed.
-- @param [WP\_Block](https://developer.wordpress.org/reference/classes/wp_block/) $wp\_block The block instance (since WP 5.5).
+- @param [WP\_Block](#reference/classes/wp_block) $wp\_block The block instance (since WP 5.5).
 - @param array $context The block context array.
 - @return void|string
 
@@ -4764,7 +4764,7 @@ Ensure a block ID always has a block\_ prefix for post meta internals.
 This directly copied from the WordPress core `serialize_block_attributes()` function.
 
 - We need this in order to make sure that block attributes are stored in a way that is  
-    consistent with how Gutenberg sends them over from JS, and so that things like [wp\_kses()](https://developer.wordpress.org/reference/functions/wp_kses/)   
+    consistent with how Gutenberg sends them over from JS, and so that things like [wp\_kses()](#reference/functions/wp_kses)   
     work as expected. Copied from core to get around a bug that was fixed in 5.8.1 or on the off chance  
     that folks are still using WP 5.3 or below.
 - TODO: Remove this when we refactor `acf_parse_save_blocks_callback()` to use `serialize_block()`,  
@@ -4812,7 +4812,7 @@ Set ACF data before a rest call if media scripts have not been enqueued yet for
 
 - @date 07/06/22
 - @since ACF 6.0
-- @param [WP\_REST\_Response](https://developer.wordpress.org/reference/classes/wp_rest_response/)|[WP\_HTTP\_Response](https://developer.wordpress.org/reference/classes/wp_http_response/)|[WP\_Error](https://developer.wordpress.org/reference/classes/wp_error/)|mixed $response The WordPress response object.
+- @param [WP\_REST\_Response](#reference/classes/wp_rest_response)|[WP\_HTTP\_Response](#reference/classes/wp_http_response)|[WP\_Error](#reference/classes/wp_error)|mixed $response The WordPress response object.
 - @return mixed
 
 ## `acf_reset_media_enqueue_after_rest()`
@@ -4821,7 +4821,7 @@ Reset wp\_enqueue\_media action count after REST call so it can happen inside th
 
 - @date 07/06/22
 - @since ACF 6.0
-- @param [WP\_REST\_Response](https://developer.wordpress.org/reference/classes/wp_rest_response/)|[WP\_HTTP\_Response](https://developer.wordpress.org/reference/classes/wp_http_response/)|[WP\_Error](https://developer.wordpress.org/reference/classes/wp_error/)|mixed $response The WordPress response object.
+- @param [WP\_REST\_Response](#reference/classes/wp_rest_response)|[WP\_HTTP\_Response](#reference/classes/wp_http_response)|[WP\_Error](#reference/classes/wp_error)|mixed $response The WordPress response object.
 - @return mixed
 
 ## `acf_block_uses_post_meta()`
@@ -4847,7 +4847,7 @@ Stores ACF field values in post meta for any blocks configured to do so.
 
 - @since ACF 6.3
 - @param integer $post\_id The ID of the post being saved.
-- @param [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/) $post The post object.
+- @param [WP\_Post](#reference/classes/wp_post) $post The post object.
 - @return void
 
 ## `acf_get_block_meta_values_to_save()`
@@ -4863,7 +4863,7 @@ that need to be saved to post meta.
 
 ---
 
-# Compatibility Global Functions
+# Compatibility Global Functions <a id="secure-custom-fields/code-reference/compatibility-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/compatibility-file/
 
@@ -4880,7 +4880,7 @@ Returns true if compatibility is enabled for the given component.
 
 ---
 
-# Deprecated Global Functions
+# Deprecated Global Functions <a id="secure-custom-fields/code-reference/deprecated-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/deprecated-file/
 
@@ -4956,7 +4956,7 @@ acf\_get\_dir
 
 ---
 
-# Fields Global Functions
+# Fields Global Functions <a id="secure-custom-fields/code-reference/fields-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields-file/
 
@@ -5095,7 +5095,7 @@ Get the PRO only fields and their core metadata.
 
 ---
 
-# L10n Global Functions
+# L10n Global Functions <a id="secure-custom-fields/code-reference/l10n-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/l10n-file/
 
@@ -5111,7 +5111,7 @@ Returns the current locale.
 
 acf\_load\_textdomain
 
-- Loads the plugin’s translated strings similar to [load\_plugin\_textdomain()](https://developer.wordpress.org/reference/functions/load_plugin_textdomain/) .
+- Loads the plugin’s translated strings similar to [load\_plugin\_textdomain()](#reference/functions/load_plugin_textdomain) .
 - @date 8/1/19
 - @since ACF 5.7.10
 - @param string $locale The plugin’s current locale.
@@ -5131,7 +5131,7 @@ acf\_load\_textdomain
 
 ---
 
-# Local Fields Global Functions
+# Local Fields Global Functions <a id="secure-custom-fields/code-reference/local-fields-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/local-fields-file/
 
@@ -5488,7 +5488,7 @@ Returns true if is a local key.
 
 ---
 
-# Local Json Global Functions
+# Local Json Global Functions <a id="secure-custom-fields/code-reference/local-json-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/local-json-file/
 
@@ -5523,7 +5523,7 @@ Deletes a field group JSON file.
 
 ---
 
-# Local Meta Global Functions
+# Local Meta Global Functions <a id="secure-custom-fields/code-reference/local-meta-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/local-meta-file/
 
@@ -5551,7 +5551,7 @@ acf\_reset\_meta
 
 ---
 
-# Locations Global Functions
+# Locations Global Functions <a id="secure-custom-fields/code-reference/locations-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/locations-file/
 
@@ -5668,7 +5668,7 @@ Alias of acf\_validate\_location\_rule().
 
 ---
 
-# Loop Global Functions
+# Loop Global Functions <a id="secure-custom-fields/code-reference/loop-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/loop-file/
 
@@ -5716,7 +5716,7 @@ alias of acf()-&gt;loop-&gt;remove\_loop()
 
 ---
 
-# Revisions Global Functions
+# Revisions Global Functions <a id="secure-custom-fields/code-reference/revisions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/revisions-file/
 
@@ -5744,7 +5744,7 @@ This function will return the latest revision for a given post
 
 ---
 
-# Scf Ui Options Page Functions Global Functions
+# Scf Ui Options Page Functions Global Functions <a id="secure-custom-fields/code-reference/scf-ui-options-page-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/scf-ui-options-page-functions-file/
 
@@ -5930,7 +5930,7 @@ Imports an ACF UI options page into the database.
 
 ---
 
-# Upgrades Global Functions
+# Upgrades Global Functions <a id="secure-custom-fields/code-reference/upgrades-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/upgrades-file/
 
@@ -6059,7 +6059,7 @@ acf\_upgrade\_550\_taxonomy
 
 ---
 
-# Validation Global Functions
+# Validation Global Functions <a id="secure-custom-fields/code-reference/validation-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/validation-file/
 
@@ -6144,7 +6144,7 @@ This function will validate a field’s value
 
 ---
 
-# API Reference
+# API Reference <a id="secure-custom-fields/features/scf-api" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/scf-api/
 
@@ -6191,7 +6191,7 @@ The Secure Custom Fields API provides programmatic access to field data and plug
 
 ---
 
-# Admin Notices Global Functions
+# Admin Notices Global Functions <a id="secure-custom-fields/code-reference/admin/admin-notices-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/admin/admin-notices-file/
 
@@ -6228,7 +6228,7 @@ Creates and returns a new notice.
 
 ---
 
-# Admin Tools Global Functions
+# Admin Tools Global Functions <a id="secure-custom-fields/code-reference/admin/admin-tools-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/admin/admin-tools-file/
 
@@ -6264,7 +6264,7 @@ This function will return the admin URL to the tools page
 
 ---
 
-# Admin
+# Admin <a id="secure-custom-fields/code-reference/admin" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/admin/
 
@@ -6275,7 +6275,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/admi
 
 ---
 
-# API Helpers Global Functions
+# API Helpers Global Functions <a id="secure-custom-fields/code-reference/api/api-helpers-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/api/api-helpers-file/
 
@@ -6378,7 +6378,7 @@ Appends data to an existing key.
 
 ## `acf_init()`
 
-Alias of acf()-&gt;[init()](https://developer.wordpress.org/reference/functions/init/) – the core ACF init function.
+Alias of acf()-&gt;[init()](#reference/functions/init) – the core ACF init function.
 
 - @since ACF 5.0.0
 
@@ -6412,7 +6412,7 @@ This function will return the url to a file within an internal ACF folder
 ## `acf_plugin_dir_url()`
 
 This function will calculate the url to a plugin folder.  
-Different to the WP [plugin\_dir\_url()](https://developer.wordpress.org/reference/functions/plugin_dir_url/) , this function can calculate for urls outside of the plugins folder (theme include).
+Different to the WP [plugin\_dir\_url()](#reference/functions/plugin_dir_url) , this function can calculate for urls outside of the plugins folder (theme include).
 
 - @since ACF 5.6.8
 - @param string $file A file path inside the ACF plugin to get the plugin directory path from.
@@ -6593,7 +6593,7 @@ acf\_get\_full\_version
 
 acf\_get\_terms
 
-- This function is a wrapper for the [get\_terms()](https://developer.wordpress.org/reference/functions/get_terms/) function
+- This function is a wrapper for the [get\_terms()](#reference/functions/get_terms) function
 - @since ACF 5.4.0
 - @param $args (array)
 - @return (array)
@@ -6664,7 +6664,7 @@ acf\_get\_numeric
 
 acf\_get\_posts
 
-- Similar to the [get\_posts()](https://developer.wordpress.org/reference/functions/get_posts/) function but with extra functionality.
+- Similar to the [get\_posts()](#reference/functions/get_posts) function but with extra functionality.
 - @since ACF 5.1.5
 - @param array $args The query args.
 - @return array
@@ -6694,7 +6694,7 @@ acf\_get\_grouped\_posts
 The internal ACF function to add order by post types for use in `acf_get_grouped_posts`
 
 - @param string $orderby The current orderby value for a query.
-- @param object $wp\_query The [WP\_Query](https://developer.wordpress.org/reference/classes/wp_query/).
+- @param object $wp\_query The [WP\_Query](#reference/classes/wp_query).
 - @return string The potentially modified orderby string.
 
 ## `acf_get_pretty_user_roles()`
@@ -6874,7 +6874,7 @@ acf\_get\_post\_id\_info
 acf\_isset\_termmeta
 
 - This function will return true if the termmeta table exists  
-    [https://developer.wordpress.org/reference/functions/get\_term\_meta/](https://developer.wordpress.org/reference/functions/get_term_meta/)
+    [\#reference/functions/get\_term\_meta](#reference/functions/get_term_meta)
 - @since ACF 5.4.0
 - @param $post\_id (int)
 - @return $post\_id (int)
@@ -6938,7 +6938,7 @@ acf\_maybe\_get
 Returns an array of attachment data.
 
 - @since ACF 5.1.5
-- @param integer|[WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/) The attachment ID or object
+- @param integer|[WP\_Post](#reference/classes/wp_post) The attachment ID or object
 - @return array|false
 
 ## `acf_get_truncated()`
@@ -7306,7 +7306,7 @@ Detect if we’re on a multisite main site.
 
 ---
 
-# API Template Global Functions
+# API Template Global Functions <a id="secure-custom-fields/code-reference/api/api-template-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/api/api-template-file/
 
@@ -7638,7 +7638,7 @@ Deprecated Functions
 
 ---
 
-# API Term Global Functions
+# API Term Global Functions <a id="secure-custom-fields/code-reference/api/api-term-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/api/api-term-file/
 
@@ -7648,7 +7648,7 @@ Returns an array of taxonomy names.
 
 - @date 7/10/13
 - @since ACF 5.0.0
-- @param array $args An array of args used in the [get\_taxonomies()](https://developer.wordpress.org/reference/functions/get_taxonomies/) function.
+- @param array $args An array of args used in the [get\_taxonomies()](#reference/functions/get_taxonomies) function.
 - @return array An array of taxonomy names.
 
 ## `acf_get_taxonomies_for_post_type()`
@@ -7677,7 +7677,7 @@ acf\_get\_term\_title
 - Returns the title for this term object.
 - @date 10/9/18
 - @since ACF 5.0.0
-- @param object $term The [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/) object.
+- @param object $term The [WP\_Term](#reference/classes/wp_term) object.
 - @return string
 
 ## `acf_get_grouped_terms()`
@@ -7687,7 +7687,7 @@ acf\_get\_grouped\_terms
 - Returns an array of terms for the given query $args and groups by taxonomy name.
 - @date 2/8/18
 - @since ACF 5.7.2
-- @param array $args An array of args used in the [get\_terms()](https://developer.wordpress.org/reference/functions/get_terms/) function.
+- @param array $args An array of args used in the [get\_terms()](#reference/functions/get_terms) function.
 - @return array
 
 ## `_acf_terms_clauses()`
@@ -7715,21 +7715,21 @@ acf\_get\_pretty\_taxonomies
 
 acf\_get\_term
 
-- Similar to [get\_term()](https://developer.wordpress.org/reference/functions/get_term/) but with some extra functionality.
+- Similar to [get\_term()](#reference/functions/get_term) but with some extra functionality.
 - @date 19/8/18
 - @since ACF 5.7.3
 - @param mixed $term\_id The term ID or a string of “taxonomy:slug”.
 - @param string $taxonomy The taxonomyname.
-- @return [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/)
+- @return [WP\_Term](#reference/classes/wp_term)
 
 ## `acf_encode_term()`
 
 acf\_encode\_term
 
-- Returns a “taxonomy:slug” string for a given [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/).
+- Returns a “taxonomy:slug” string for a given [WP\_Term](#reference/classes/wp_term).
 - @date 27/8/18
 - @since ACF 5.7.4
-- @param [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/) $term The term object.
+- @param [WP\_Term](#reference/classes/wp_term) $term The term object.
 - @return string
 
 ## `acf_decode_term()`
@@ -7739,14 +7739,14 @@ acf\_decode\_term
 - Decodes a “taxonomy:slug” string into an array of taxonomy and slug.
 - @date 27/8/18
 - @since ACF 5.7.4
-- @param [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/) $term The term object.
+- @param [WP\_Term](#reference/classes/wp_term) $term The term object.
 - @return string
 
 ## `acf_get_encoded_terms()`
 
 acf\_get\_encoded\_terms
 
-- Returns an array of [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/) objects from an array of encoded strings
+- Returns an array of [WP\_Term](#reference/classes/wp_term) objects from an array of encoded strings
 - @date 9/9/18
 - @since ACF 5.7.5
 - @param array $values The array of encoded strings.
@@ -7781,7 +7781,7 @@ acf\_get\_choice\_from\_term
 - Returns an array containing the id and text for this item.
 - @date 10/9/18
 - @since ACF 5.7.6
-- @param object $item The item object such as [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/) or [WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/).
+- @param object $item The item object such as [WP\_Post](#reference/classes/wp_post) or [WP\_Term](#reference/classes/wp_term).
 - @param string $format The value format (term\_id, slug)
 - @return array
 
@@ -7801,7 +7801,7 @@ No longer needed since WP introduced the termmeta table in WP 4.4.
 
 ---
 
-# ACF_Repeater_Table
+# ACF_Repeater_Table <a id="secure-custom-fields/code-reference/fields/class-acf-repeater-table-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/fields/class-acf-repeater-table-file/
 
@@ -7926,14 +7926,14 @@ Renders the actions displayed underneath the table.
 ### `pagination`
 
 Renders the table pagination.  
-Mostly lifted from the WordPress core [WP\_List\_Table](https://developer.wordpress.org/reference/classes/wp_list_table/) class.
+Mostly lifted from the WordPress core [WP\_List\_Table](#reference/classes/wp_list_table) class.
 
 - @since ACF 6.0.0
 - @return void
 
 ---
 
-# Form Front Global Functions
+# Form Front Global Functions <a id="secure-custom-fields/code-reference/form-front-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/form-front-file/
 
@@ -7952,7 +7952,7 @@ Functions
 
 ---
 
-# Forms
+# Forms <a id="secure-custom-fields/code-reference/forms" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/forms/
 
@@ -7962,7 +7962,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/form
 
 ---
 
-# Hooks
+# Hooks <a id="secure-custom-fields/code-reference/hooks" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/hooks/
 
@@ -7973,7 +7973,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/hook
 
 ---
 
-# Acf Rest API Functions Global Functions
+# Acf Rest API Functions Global Functions <a id="secure-custom-fields/code-reference/class-acf-rest-api-file/acf-rest-api-functions-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/class-acf-rest-api-file/acf-rest-api-functions-file/
 
@@ -7991,7 +7991,7 @@ and provide API resource links to related objects. If a link is marked as ’emb
 in the main request under the\_embedded property when the request contains the \_embed URL parameter.
 
 - @see \\acf\_field::get\_rest\_links()  
-    @see <https://developer.wordpress.org/rest-api/using-the-rest-api/linking-and-embedding/>
+    @see [\#rest-api/using-the-rest-api/linking-and-embedding](#rest-api/using-the-rest-api/linking-and-embedding)
 - @param string|integer $post\_id
 - @param array $field
 - @return array
@@ -8010,7 +8010,7 @@ Format a given field’s value for output in the REST API.
 
 ---
 
-# ACF_Rest_Api
+# ACF_Rest_Api <a id="secure-custom-fields/code-reference/class-acf-rest-api-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/class-acf-rest-api-file/
 
@@ -8045,9 +8045,9 @@ fires off a filter, so we can add some custom validation for specific fields.
     and `sanitize_callback` for nested schema properties, see:  
     <https://core.trac.wordpress.org/ticket/49960>
 - @param mixed $value
-- @param \\[WP\_REST\_Request](https://developer.wordpress.org/reference/classes/wp_rest_request/) $request
+- @param \\[WP\_REST\_Request](#reference/classes/wp_rest_request) $request
 - @param string $param
-- @return boolean|[WP\_Error](https://developer.wordpress.org/reference/classes/wp_error/)
+- @return boolean|[WP\_Error](#reference/classes/wp_error)
 
 ### `load_fields`
 
@@ -8056,7 +8056,7 @@ it is required by WordPress.
 
 - @param array $object An array representation of the post, term, or user object.
 - @param string $field\_name
-- @param [WP\_REST\_Request](https://developer.wordpress.org/reference/classes/wp_rest_request/) $request
+- @param [WP\_REST\_Request](#reference/classes/wp_rest_request) $request
 - @param string $object\_sub\_type Note that this isn’t the same as $this-&gt;object\_type. This variable is  
     more specific and can be a post type or taxonomy.
 - @return array
@@ -8067,11 +8067,11 @@ Update any incoming field values for the given object. This method is not a part
 public as it is required by WordPress.
 
 - @param array $data
-- @param [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/)|[WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/)|[WP\_User](https://developer.wordpress.org/reference/classes/wp_user/) $object
+- @param [WP\_Post](#reference/classes/wp_post)|[WP\_Term](#reference/classes/wp_term)|[WP\_User](#reference/classes/wp_user) $object
 - @param string $property ‘acf’
-- @param [WP\_REST\_Request](https://developer.wordpress.org/reference/classes/wp_rest_request/) $request
+- @param [WP\_REST\_Request](#reference/classes/wp_rest_request) $request
 - @param string $object\_sub\_type This will be the post type, the taxonomy, or ‘user’.
-- @return boolean|[WP\_Error](https://developer.wordpress.org/reference/classes/wp_error/)
+- @return boolean|[WP\_Error](#reference/classes/wp_error)
 
 ### `make_identifier`
 
@@ -8118,7 +8118,7 @@ Get all ACF fields for a given field group and allow third party filtering.
 
 ---
 
-# ACF_Rest_Embed_Links
+# ACF_Rest_Embed_Links <a id="secure-custom-fields/code-reference/class-acf-rest-api-file/class-acf-rest-embed-links-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/class-acf-rest-api-file/class-acf-rest-embed-links-file/
 
@@ -8149,14 +8149,14 @@ Add links to internal property for subsequent use in \\ACF\_Rest\_Embed\_Links::
 
 Hook into the rest\_prepare\_{$type} filters and add links for the object being prepared.
 
-- @param [WP\_REST\_Response](https://developer.wordpress.org/reference/classes/wp_rest_response/) $response
-- @param [WP\_Post](https://developer.wordpress.org/reference/classes/wp_post/)|[WP\_User](https://developer.wordpress.org/reference/classes/wp_user/)|[WP\_Term](https://developer.wordpress.org/reference/classes/wp_term/) $item
-- @param [WP\_REST\_Request](https://developer.wordpress.org/reference/classes/wp_rest_request/) $request
-- @return [WP\_REST\_Response](https://developer.wordpress.org/reference/classes/wp_rest_response/)
+- @param [WP\_REST\_Response](#reference/classes/wp_rest_response) $response
+- @param [WP\_Post](#reference/classes/wp_post)|[WP\_User](#reference/classes/wp_user)|[WP\_Term](#reference/classes/wp_term) $item
+- @param [WP\_REST\_Request](#reference/classes/wp_rest_request) $request
+- @return [WP\_REST\_Response](#reference/classes/wp_rest_response)
 
 ---
 
-# ACF_Rest_Request
+# ACF_Rest_Request <a id="secure-custom-fields/code-reference/class-acf-rest-api-file/class-acf-rest-request-file" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/class-acf-rest-api-file/class-acf-rest-request-file/
 
@@ -8246,18 +8246,18 @@ object type as well as post type or taxonomy in order to provide the right conte
 Find the REST enabled post type object that matches the given REST base.
 
 - @param string $rest\_base
-- @return [WP\_Post\_Type](https://developer.wordpress.org/reference/classes/wp_post_type/)|null
+- @return [WP\_Post\_Type](#reference/classes/wp_post_type)|null
 
 ### `get_taxonomy_by_rest_base`
 
 Find the REST enabled taxonomy object that matches the given REST base.
 
 - @param $rest\_base
-- @return [WP\_Taxonomy](https://developer.wordpress.org/reference/classes/wp_taxonomy/)|null
+- @return [WP\_Taxonomy](#reference/classes/wp_taxonomy)|null
 
 ---
 
-# REST API
+# REST API <a id="secure-custom-fields/code-reference/rest-api" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/code-reference/rest-api/
 
@@ -8270,7 +8270,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/code-reference/rest
 
 ---
 
-# Field Types
+# Field Types <a id="secure-custom-fields/features/field" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/
 
@@ -8319,7 +8319,7 @@ Each field type has its own documentation and tutorial showing how to implement
 
 ---
 
-# Repeater Field
+# Repeater Field <a id="secure-custom-fields/features/field/repeater" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/repeater/
 
@@ -8343,7 +8343,7 @@ The Repeater field allows you to create a set of sub fields which can be repeate
 
 ---
 
-# Using the Repeater Field
+# Using the Repeater Field <a id="secure-custom-fields/features/field/repeater/repeater-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/repeater/repeater-tutorial/
 
@@ -8377,7 +8377,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/repe
 
 ---
 
-# Select Field
+# Select Field <a id="secure-custom-fields/features/field/select" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/select/
 
@@ -8401,7 +8401,7 @@ The Select field provides a dropdown interface for selecting single or multiple
 
 ---
 
-# Using the Select Field
+# Using the Select Field <a id="secure-custom-fields/features/field/select/select-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/select/select-tutorial/
 
@@ -8435,7 +8435,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/sele
 
 ---
 
-# Separator Field
+# Separator Field <a id="secure-custom-fields/features/field/separator" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/separator/
 
@@ -8457,7 +8457,7 @@ The Separator field provides visual separation between fields in the editing int
 
 ---
 
-# Using the Separator Field
+# Using the Separator Field <a id="secure-custom-fields/features/field/separator/separator-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/separator/separator-tutorial/
 
@@ -8491,7 +8491,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/sepa
 
 ---
 
-# Tab Field
+# Tab Field <a id="secure-custom-fields/features/field/tab" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/tab/
 
@@ -8514,7 +8514,7 @@ The Tab field creates navigation tabs to organize fields into sections. It impro
 
 ---
 
-# Using the Tab Field
+# Using the Tab Field <a id="secure-custom-fields/features/field/tab/tab-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/tab/tab-tutorial/
 
@@ -8548,7 +8548,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/tab/
 
 ---
 
-# Taxonomy Field
+# Taxonomy Field <a id="secure-custom-fields/features/field/taxonomy" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/taxonomy/
 
@@ -8572,7 +8572,7 @@ The Taxonomy field creates an interface for selecting taxonomy terms. It support
 
 ---
 
-# Using the Taxonomy Field
+# Using the Taxonomy Field <a id="secure-custom-fields/features/field/taxonomy/taxonomy-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/taxonomy/taxonomy-tutorial/
 
@@ -8606,7 +8606,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/taxo
 
 ---
 
-# Text Field
+# Text Field <a id="secure-custom-fields/features/field/text" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/text/
 
@@ -8630,7 +8630,7 @@ The Text field provides a standard single-line text input with various formattin
 
 ---
 
-# Using the Text Field
+# Using the Text Field <a id="secure-custom-fields/features/field/text/text-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/text/text-tutorial/
 
@@ -8666,7 +8666,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/text
 
 ---
 
-# Textarea Field
+# Textarea Field <a id="secure-custom-fields/features/field/textarea" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/textarea/
 
@@ -8690,7 +8690,7 @@ The Textarea field provides a multi-line text input for longer content with form
 
 ---
 
-# Using the Textarea Field
+# Using the Textarea Field <a id="secure-custom-fields/features/field/textarea/textarea-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/textarea/textarea-tutorial/
 
@@ -8726,7 +8726,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/text
 
 ---
 
-# Time Picker Field
+# Time Picker Field <a id="secure-custom-fields/features/field/time-picker" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/time-picker/
 
@@ -8750,7 +8750,7 @@ The Time Picker field provides an interface for selecting time values with custo
 
 ---
 
-# Using the Time Picker Field
+# Using the Time Picker Field <a id="secure-custom-fields/features/field/time-picker/time-picker-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/time-picker/time-picker-tutorial/
 
@@ -8784,7 +8784,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/time
 
 ---
 
-# True/False Field
+# True/False Field <a id="secure-custom-fields/features/field/true-false" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/true-false/
 
@@ -8808,7 +8808,7 @@ The True/False field provides a simple toggle switch for boolean values. It offe
 
 ---
 
-# Using the True/False Field
+# Using the True/False Field <a id="secure-custom-fields/features/field/true-false/true-false-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/true-false/true-false-tutorial/
 
@@ -8842,7 +8842,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/true
 
 ---
 
-# URL Field
+# URL Field <a id="secure-custom-fields/features/field/url" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/url/
 
@@ -8865,7 +8865,7 @@ The URL field provides input for web addresses with validation and formatting op
 
 ---
 
-# Using the URL Field
+# Using the URL Field <a id="secure-custom-fields/features/field/url/url-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/url/url-tutorial/
 
@@ -8899,7 +8899,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/url/
 
 ---
 
-# User Field
+# User Field <a id="secure-custom-fields/features/field/user" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/user/
 
@@ -8923,7 +8923,7 @@ The User field creates an interface for selecting WordPress users. It supports m
 
 ---
 
-# Using the User Field
+# Using the User Field <a id="secure-custom-fields/features/field/user/user-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/user/user-tutorial/
 
@@ -8957,7 +8957,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/user
 
 ---
 
-# WYSIWYG Field
+# WYSIWYG Field <a id="secure-custom-fields/features/field/wysiwyg" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/wysiwyg/
 
@@ -8981,7 +8981,7 @@ The WYSIWYG (What You See Is What You Get) field provides a rich text editor wit
 
 ---
 
-# Using the WYSIWYG Field
+# Using the WYSIWYG Field <a id="secure-custom-fields/features/field/wysiwyg/wysiwyg-tutorial" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/features/field/wysiwyg/wysiwyg-tutorial/
 
@@ -9015,7 +9015,7 @@ Source: https://developer.wordpress.org/secure-custom-fields/features/field/wysi
 
 ---
 
-# Getting Started with Secure Custom Fields
+# Getting Started with Secure Custom Fields <a id="secure-custom-fields" />
 
 Source: https://developer.wordpress.org/secure-custom-fields/
 

diff --git a/wp-theme-handbook.md b/wp-theme-handbook.md
diff --git a/wp-wpcs-handbook.md b/wp-wpcs-handbook.md
@@ -1,4 +1,4 @@
-# Markdown Style Guide
+# Markdown Style Guide <a id="coding-standards/styleguide" />
 
 Source: https://developer.wordpress.org/coding-standards/styleguide/
 
@@ -231,25 +231,25 @@ This is _italic text_. This is **bold text**.
 
 ---
 
-# Best Practices
+# Best Practices <a id="coding-standards" />
 
 Source: https://developer.wordpress.org/coding-standards/
 
 WordPress is a big project with thousands of contributors. It’s important that best practices are followed so that the codebase is consistent and readable, and changes are easy to find and read, whether the code is five days old or five years old. What follows are a series of best practices to help keep WordPress code clean and well documented for years to come.
 
-- [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/)
-    - [Accessibility Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/)
-    - [CSS Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/)
-    - [HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/)
-    - [JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
-    - [PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
-- [Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/)
-    - [JavaScript Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/javascript/)
-    - [PHP Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/)
+- [WordPress Coding Standards](#coding-standards/wordpress-coding-standards)
+    - [Accessibility Coding Standards](#coding-standards/wordpress-coding-standardsaccessibility/)
+    - [CSS Coding Standards](#coding-standards/wordpress-coding-standardscss/)
+    - [HTML Coding Standards](#coding-standards/wordpress-coding-standardshtml/)
+    - [JavaScript Coding Standards](#coding-standards/wordpress-coding-standardsjavascript/)
+    - [PHP Coding Standards](#coding-standards/wordpress-coding-standardsphp/)
+- [Inline Documentation Standards](#coding-standards/inline-documentation-standards)
+    - [JavaScript Documentation Standards](#coding-standards/inline-documentation-standardsjavascript/)
+    - [PHP Documentation Standards](#coding-standards/inline-documentation-standardsphp/)
 
 ---
 
-# WordPress Coding Standards
+# WordPress Coding Standards <a id="coding-standards/wordpress-coding-standards" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/
 
@@ -267,22 +267,22 @@ If you are planning to contribute to WordPress core, you need to familiarize you
 
 ## Language-specific Standards
 
-- [CSS Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/)
-- [HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/)
-- [JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
-- [PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
+- [CSS Coding Standards](#coding-standards/wordpress-coding-standards/css)
+- [HTML Coding Standards](#coding-standards/wordpress-coding-standards/html)
+- [JavaScript Coding Standards](#coding-standards/wordpress-coding-standards/javascript)
+- [PHP Coding Standards](#coding-standards/wordpress-coding-standards/php)
 
 ## Accessibility Standards
 
-WordPress is committed to meeting the [Web Content Accessibility Guidelines (WCAG) at level AA](https://www.w3.org/TR/WCAG20/) for all new and updated code. We’ve provided a [quick guide to common accessibility issues](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/) you should be aware of when creating patches or feature plug-ins.
+WordPress is committed to meeting the [Web Content Accessibility Guidelines (WCAG) at level AA](https://www.w3.org/TR/WCAG20/) for all new and updated code. We’ve provided a [quick guide to common accessibility issues](#coding-standards/wordpress-coding-standards/accessibility) you should be aware of when creating patches or feature plug-ins.
 
 ## Where do the coding standards \_not\_ apply?
 
 Third-party libraries are not subject to these standards, even when integrated with the primary project. This includes instances like WordPress core, where multiple third-party libraries are incorporated into its codebase.
 
 ---
 
-# Accessibility Coding Standards
+# Accessibility Coding Standards <a id="coding-standards/wordpress-coding-standards/accessibility" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/
 
@@ -439,7 +439,7 @@ For more information on techniques, visit [Understanding Techniques for WCAG Suc
 
 ---
 
-# CSS Coding Standards
+# CSS Coding Standards <a id="coding-standards/wordpress-coding-standards/css" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/
 
@@ -483,7 +483,7 @@ Incorrect:
 
 With specificity, comes great responsibility. Broad selectors allow us to be efficient, yet can have adverse consequences if not tested. Location-specific selectors can save us time, but will quickly lead to a cluttered stylesheet. Exercise your best judgement to create selectors that find the right balance between contributing to the overall style and layout of the DOM.
 
-- Similar to the [WordPress PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#naming-conventions) for file names, use lowercase and separate words with hyphens when naming selectors. Avoid camelcase and underscores.
+- Similar to the [WordPress PHP Coding Standards](#coding-standards/wordpress-coding-standards/php) for file names, use lowercase and separate words with hyphens when naming selectors. Avoid camelcase and underscores.
 - Use human readable selectors that describe what element(s) they style.
 - Attribute selectors should use double quotes around values.
 - Refrain from using over-qualified selectors, `div.container` can simply be stated as `.container`.
@@ -757,7 +757,7 @@ Check out the [WP Admin CSS Audit](https://wordpress.github.io/css-audit/public/
 
 ---
 
-# HTML Coding Standards
+# HTML Coding Standards <a id="coding-standards/wordpress-coding-standards/html" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/
 
@@ -880,7 +880,7 @@ Incorrect:
 
 ---
 
-# JavaScript Coding Standards
+# JavaScript Coding Standards <a id="coding-standards/wordpress-coding-standards/javascript" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/
 
@@ -1182,7 +1182,7 @@ window.wp = window.wp || {};
 
 ## Naming Conventions
 
-Variable and function names should be full words, using camel case with a lowercase first letter. This is an area where this standard differs from the [WordPress PHP coding standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#naming-conventions).
+Variable and function names should be full words, using camel case with a lowercase first letter. This is an area where this standard differs from the [WordPress PHP coding standards](#coding-standards/wordpress-coding-standards/php).
 
 Names should be descriptive, but not excessively so. Exceptions are allowed for iterators, such as the use of `i` to represent the index in a loop.
 
@@ -1515,7 +1515,7 @@ if ( typeof jQuery.fn.hoverIntent === 'undefined' ) {
 
 ---
 
-# PHP Coding Standards
+# PHP Coding Standards <a id="coding-standards/wordpress-coding-standards/php" />
 
 Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/
 
@@ -1525,7 +1525,7 @@ While themes and plugins may choose to follow a different *coding style*, these
 
 While not all code may fully comply with these standards (yet), all newly committed and/or updated code should fully comply with these coding standards.
 
-Also see the [PHP Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/) for further guidelines.
+Also see the [PHP Inline Documentation Standards](#coding-standards/inline-documentation-standards/php) for further guidelines.
 
 If you want to automatically check your code against this standard, you can use the official [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards) tooling, which is run using [PHP\_CodeSniffer](https://github.com/PHPCSStandards/PHP_CodeSniffer/).
 
@@ -1601,7 +1601,7 @@ echo "<a href='{$escaped_link}'>text with a ' single quote</a>";
 
 ```
 
-Text that goes into HTML or XML attributes should be escaped so that single or double quotes do not end the attribute value and invalidate the HTML, causing a security issue. See [Data Validation](https://developer.wordpress.org/plugins/security/data-validation/) in the Plugin Handbook for further details.
+Text that goes into HTML or XML attributes should be escaped so that single or double quotes do not end the attribute value and invalidate the HTML, causing a security issue. See [Data Validation](#plugins/security/data-validation) in the Plugin Handbook for further details.
 
 ### Writing require/include statements
 
@@ -1977,8 +1977,6 @@ function baz(Class_Name $param_a, String$param_b,      CALLABLE     $param_c )
 
 ```
 
-
-
 Type declaration usage has the following restrictions based on the minimum required PHP version of an application, whether it is WordPress Core, a plugin or a theme:
 
 - The scalar `bool`, `int`, `float`, and `string` type declarations cannot be used until the minimum PHP version is PHP 7.0 or higher.
@@ -1994,20 +1992,11 @@ Type declaration usage has the following restrictions based on the minimum requi
 - `never` (return type only) cannot be used until the minimum PHP version is PHP 8.1 or higher.
 - Disjunctive normal form types (combining union types and intersection types) cannot be used until the minimum PHP version is PHP 8.2 or higher.
 
-
-
-
-
 *Usage in WordPress Core*
 
-
-
   
 Adding type declarations to existing WordPress Core functions should be done with extreme care.  
 
-
-
-
 The function signature of any function (method) which can be overloaded by plugins or themes should not be touched.  
 This leaves, for now, only unconditionally declared functions in the global namespace, `private` class methods, and code new to Core, as candidates for adding type declarations.
 
@@ -2057,15 +2046,10 @@ function fool( &   ... $spread ) {
 
 ```
 
-
-
   
 The spread operator (or splat operator as it’s known in other languages) can be used for packing arguments in function declarations (variadic functions) and unpacking them in function calls as of PHP 5.6. Since PHP 7.4, the spread operator is also used for unpacking numerically-indexed arrays, with string-keyed array unpacking available since PHP 8.1.  
 When used in a function declaration, the spread operator can only be used with the last parameter.  
 
-
-
-
 ## Declare Statements, Namespace, and Import Statements
 
 ### Namespace declarations
@@ -2100,23 +2084,13 @@ The use of namespaces in plugins and themes is strongly encouraged. It is a grea
 
 Please do make sure you use a unique and long enough namespace prefix to actually prevent conflicts. Generally speaking, using a namespace prefix along the lines of `Vendor\Project_Name` is a good idea.
 
-
-
   
 The `wp` and `WordPress` namespace prefixes are reserved for WordPress itself.  
 
-
-
-
-
-
   
 Namespacing has no effect on variables, constants declared with `define()` or non-PHP native constructs, like the hook names as used in WordPress.  
 Those still need to be prefixed individually.  
 
-
-
-
 ### Using import `use` statements
 
 Using import `use` statements allows you to refer to constants, functions, classes, interfaces, namespaces, enums and traits that live outside of the current namespace.
@@ -2178,24 +2152,14 @@ use function Project_Name\Sub_Feature\function_b as Aliased_Function; // Import
 
 ```
 
-
-
 
 Import `use` statements have no effect on dynamic class, function or constant names.  
 Group `use` statements are available from PHP 7.0, and trailing commas in group `use` statements are available from PHP 7.2.  
 
-
-
-
-
-
 
 Note that, unless you have implemented [autoloading](https://www.php.net/manual/en/language.oop5.autoload.php), the `use` statement won’t automatically load whatever is being imported. For OO constructs, you’ll either need to set up autoloading or load the file(s) containing the OO declaration(s) using `require[_once]` or `include[_once]` statement(s).  
 Autoloading is only applicable to OO constructs; for functions and constants, you must always use `require[_once]` or `include[_once]`.  
 
-
-
-
 **Note about WordPress Core usage**
 
 While import `use` statements can already be used in WordPress Core, it is, for the moment, **strongly discouraged**.
@@ -2350,18 +2314,13 @@ class Foo {
 
 ```
 
-
-
 
 – Visibility for OO constants can be declared since PHP 7.1.  
 – Typed properties are available since PHP 7.4.  
 – Readonly properties are available since PHP 8.1.  
 – `final` modifier for constants in object-oriented structures is available since PHP 8.1.  
 – Readonly classes are available since PHP 8.2.  
 
-
-
-
 ### Object Instantiation
 
 When instantiating a new object instance, parenthesis must always be used, even when not strictly necessary.  
@@ -2478,7 +2437,7 @@ The following placeholders can be used in the query string:
 
 Note that these placeholders should not be ‘quoted’! `$wpdb->prepare()` will take care of escaping and quoting for us. This makes it easy to see at a glance whether something has been escaped or not because it happens right when the query happens.
 
-See [Data Validation](https://developer.wordpress.org/plugins/security/data-validation/) in the Plugin Handbook for further details.
+See [Data Validation](#plugins/security/data-validation) in the Plugin Handbook for further details.
 
 ## Recommendations
 
@@ -2645,26 +2604,26 @@ Use of the backtick operator is identical to [`shell_exec()`](https://www.php.ne
 
 ---
 
-# Inline Documentation Standards
+# Inline Documentation Standards <a id="coding-standards/inline-documentation-standards" />
 
 Source: https://developer.wordpress.org/coding-standards/inline-documentation-standards/
 
-Inline documentation provides a good resource for core developers in future development, and other developers when learning about WordPress. It also provides the information necessary to populate the [WordPress developer code reference](https://developer.wordpress.org/reference/).
+Inline documentation provides a good resource for core developers in future development, and other developers when learning about WordPress. It also provides the information necessary to populate the [WordPress developer code reference](#reference).
 
 > **I don’t need to document my code. I wrote all of it – know it like the back of my hand.**“I would argue that, separately, documentation *is also* for you, the developer. I’ve found quite often that my inline documentation can be a very effective breadcrumb trail when establishing one’s own intent, particularly with regard to complex function arguments and usage. And it’s also helpful to return to a function two years later and find a paragraph in the inline documentation that describes, in meticulous fashion, something that I otherwise would have had to rediscover all over again.” *– Nacin*
 
 ## Language-specific Standards
 
-- [PHP Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/ "PHP Documentation Standards")
-- [JavaScript Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/javascript/)
+- [PHP Documentation Standards](#coding-standards/inline-documentation-standards/php "PHP Documentation Standards")
+- [JavaScript Documentation Standards](#coding-standards/inline-documentation-standards/javascript)
 
 ## Resources
 
 - [Inline documentation](https://jjj.blog/2012/06/inline-documentation/) – why you should
 
 ---
 
-# JavaScript Documentation Standards
+# JavaScript Documentation Standards <a id="coding-standards/inline-documentation-standards/javascript" />
 
 Source: https://developer.wordpress.org/coding-standards/inline-documentation-standards/javascript/
 
@@ -2692,17 +2651,11 @@ Short descriptions should be clear, simple, and brief. Document “what” and
 
 Functions and closures are *third-person singular* elements, meaning *third-person singular verbs* should be used to describe what each does.
 
-
-
 Need help remembering how to conjugate for third-person singular verbs? Imagine prefixing the function, hook, class, or method summary with “It”:
 
 - *Good*: “(It) Does something.”
 - *Bad:* “(It) Do something.”
 
-
-
-
-
 **Functions**: What does the function do?
 
 - *Good*: Handles a click on X element.
@@ -3141,7 +3094,7 @@ WordPress uses JSHint for general code quality testing. Any inline configuration
 
 ---
 
-# PHP Documentation Standards
+# PHP Documentation Standards <a id="coding-standards/inline-documentation-standards/php" />
 
 Source: https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/
 
@@ -3167,10 +3120,6 @@ Summaries should be clear, simple, and brief. Avoid describing “why” an elem
 Need help remembering how to conjugate for third-person singular verbs? Imagine prefixing the function, hook, class, or method summary with “It”: - *Good*: “(It) Does something.”
 - *Bad*: “(It) Do something.”
 
-
-
-
-
 Summary examples: - **Functions**: *What* does the function do? 
     - Good: *Displays the last modified date for a post.*
     - Bad: *Display the date on which the post was last modified.*
@@ -3187,11 +3136,7 @@ Descriptive elements should be written as complete sentences. The one exception
 
 **`@since`**: The recommended tool to use when searching for the version something was added to WordPress is [`svn blame`](https://make.wordpress.org/core/handbook/svn/code-history/#using-subversion-annotate). An additional resource for older hooks is the [WordPress Hooks Database](http://adambrown.info/p/wp_hooks). If the version number cannot be determined after using these tools, use `@since Unknown`. Anything ported over from WPMU should use `@since MU (3.0.0)`. Existing `@since MU (3.0.0)` tags should not be changed. **Code Refactoring**: It is permissible to space out the specific action or filter lines being documented to meet the coding standards, but do not refactor other code in the file. ### Formatting Guidelines
 
-
-
-WordPress’ inline documentation standards for PHP are specifically tailored for optimum output on the [official Code Reference](https://developer.wordpress.org/reference/). As such, following the standards in core and formatting as described below are *extremely* important to ensure expected output. 
-
-
+WordPress’ inline documentation standards for PHP are specifically tailored for optimum output on the [official Code Reference](#reference). As such, following the standards in core and formatting as described below are *extremely* important to ensure expected output. 
 
 #### General
 
@@ -3266,8 +3211,8 @@ PHPDoc supports multiple `@since` versions in DocBlocks for this explicit reason
 #### Other Descriptions
 
 `@param`, `@type`, `@return`: No HTML should be used in the descriptions for these tags, though limited Markdown can be used as necessary, such as for adding backticks around variables, e.g. `$variable`. - Inline `@see` tags can also be used to auto-link hooks in core: 
-    - Hooks, e.g. `<a href="https://developer.wordpress.org/reference/hooks/save_post/">'save_post'</a>`
-    - Dynamic hooks, e.g. `<a href="https://developer.wordpress.org/reference/hooks/old_status_to_new_status/">'$old_status_to_$new_status'</a>` (Note that any extra curly braces have been removed inside the quotes)
+    - Hooks, e.g. `<a href="#referencehooks/save_post/">'save_post'</a>`
+    - Dynamic hooks, e.g. `<a href="#referencehooks/old_status_to_new_status/">'$old_status_to_$new_status'</a>` (Note that any extra curly braces have been removed inside the quotes)
 - Default or available values should use single quotes, e.g. ‘draft’. Translatable strings should be identified as such in the description.
 - HTML elements and tags should be written as “audio element” or “link tag”.
 
@@ -3310,7 +3255,7 @@ Functions and class methods should be formatted as follows: - **Summary**: A bri
 
 #### 1.1 Parameters That Are Arrays
 
-Parameters that are an array of arguments should be documented in the “originating” function only, and cross-referenced via an `@see` tag in corresponding DocBlocks. Array values should be documented using WordPress’ flavor of hash notation style similar to how [Hooks](https://developer.wordpress.org/coding-standards/inline-documentation-standards/php/#4-hooks-actions-and-filters) can be documented, each array value beginning with the `@type` tag, and taking the form of: ```php
+Parameters that are an array of arguments should be documented in the “originating” function only, and cross-referenced via an `@see` tag in corresponding DocBlocks. Array values should be documented using WordPress’ flavor of hash notation style similar to how [Hooks](#coding-standards/inline-documentation-standards/php) can be documented, each array value beginning with the `@type` tag, and taking the form of: ```php
 *     @type type $key Description. Default 'value'. Accepts 'value', 'value'.
 *                     (aligned with Description, if wraps to a new line)
 
@@ -3509,10 +3454,10 @@ The file header DocBlock is used to give an overview of what is contained in the
 
 ```
 
-The *Summary* section is meant to serve as a succinct description of **what** specific purpose the file serves. Examples: - Good: *“Widgets API: [WP\_Widget](https://developer.wordpress.org/reference/classes/wp_widget/) class”*
+The *Summary* section is meant to serve as a succinct description of **what** specific purpose the file serves. Examples: - Good: *“Widgets API: [WP\_Widget](#referenceclasses/wp_widget/) class”*
 - Bad: *“Core widgets class”*
 
-The *Description* section can be used to better explain overview information for the file such as how the particular file fits into the overall makeup of an API or component. Examples: - Good: *“The Widgets API is comprised of the [WP\_Widget](https://developer.wordpress.org/reference/classes/wp_widget/) and [WP\_Widget\_Factory](https://developer.wordpress.org/reference/classes/wp_widget_factory/) classes in addition to a variety of top-level functionality that implements the Widgets and related sidebar APIs. WordPress registers a number of common widgets by default.”*
+The *Description* section can be used to better explain overview information for the file such as how the particular file fits into the overall makeup of an API or component. Examples: - Good: *“The Widgets API is comprised of the [WP\_Widget](#referenceclasses/wp_widget/) and [WP\_Widget\_Factory](#referenceclasses/wp_widget_factory/) classes in addition to a variety of top-level functionality that implements the Widgets and related sidebar APIs. WordPress registers a number of common widgets by default.”*
 
 ### 7. Constants
 
@@ -3554,16 +3499,12 @@ Common PHPDoc tags used in WordPress include `@since`, `@see`, `@global` `@param
 | **`@uses`** | class::methodname() / class::$variablename / functionname() | Note: This tag has been used in the past, but should no longer be used. References a key function/method used. May include a short description. |
 | **`@var`** | datatype description | Data type for a class variable and short description. Callbacks are marked callback. |
 
-
-
 PHPDoc tags work with some text editors/IDEs to display more information about a piece of code. It is useful to developers using those editors to understand what the purpose is, and where they would use it in their code. PhpStorm and Netbeans already support PHPDoc. The following text editors/IDEs have extensions/bundles you can install that will help you auto-create DocBlocks: - Notepad++: [DocIt for Notepad++](http://sourceforge.net/projects/nppdocit/) (Windows)
 - TextMate: [php.tmbundle](https://github.com/textmate/php.tmbundle) (Mac)
 - SublimeText: [sublime packages](https://packagecontrol.io/search/phpdoc) (Windows, Mac, Linux)
 
 Note: Even with help generating DocBlocks, most code editors don’t do a very thorough job – it’s likely you’ll need to manually fill in certain areas of any generated DocBlocks. 
 
-
-
 ### Deprecated Tags
 
 > **Preface:** For the time being, and for the sake of consistency, WordPress Core will continue to use `@subpackage` tags – both when writing new DocBlocks, and editing old ones. Only when the new – external – PSR-5 recommendations are finalized, will across-the-board changes be considered, such as deprecating certain tags.
@@ -3588,7 +3529,7 @@ As proposed in the [new PSR-5](https://github.com/phpDocumentor/fig-standards/bl
 
 ---
 
-# Changelog
+# Changelog <a id="coding-standards/changelog" />
 
 Source: https://developer.wordpress.org/coding-standards/changelog/
 

diff --git a/wp-adv-admin-handbook.md b/wp-adv-admin-handbook.md
diff --git a/wp-apis-handbook.md b/wp-apis-handbook.md
diff --git a/wp-blocks-handbook.md b/wp-blocks-handbook.md
diff --git a/wp-plugin-handbook.md b/wp-plugin-handbook.md
diff --git a/wp-rest-api-handbook.md b/wp-rest-api-handbook.md
diff --git a/wp-scf-handbook.md b/wp-scf-handbook.md
diff --git a/wp-theme-handbook.md b/wp-theme-handbook.md
diff --git a/wp-wpcs-handbook.md b/wp-wpcs-handbook.md
diff --git a/wp-handbooks.md b/wp-handbooks.md