diff --git a/docs/content/docs/group_patch.mdx b/docs/content/docs/group_patch.mdx
new file mode 100644
index 0000000..ef8e491
--- /dev/null
+++ b/docs/content/docs/group_patch.mdx
@@ -0,0 +1,28 @@
+---
+title: group_patch
+full: true
+_openapi:
+ method: PATCH
+ route: group_patch
+ toc: []
+ structuredData:
+ headings: []
+ contents:
+ - content: >
+ Patch a group.
+
+
+ The difference between the update and patch methods is that the patch
+ will perform an update of the provided parameters, while leaving all
+ other parameters unchanged, whereas the update methods deletes all
+ parameters not explicitly provided in the data_dict.
+---
+
+{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}
+
+Patch a group.
+
+The difference between the update and patch methods is that the patch will perform an update of the provided parameters, while leaving all other parameters unchanged, whereas the update methods deletes all parameters not explicitly provided in the data_dict.
+
+
+
\ No newline at end of file
diff --git a/docs/content/docs/organization_patch.mdx b/docs/content/docs/organization_patch.mdx
new file mode 100644
index 0000000..0ffd07c
--- /dev/null
+++ b/docs/content/docs/organization_patch.mdx
@@ -0,0 +1,28 @@
+---
+title: organization_patch
+full: true
+_openapi:
+ method: PATCH
+ route: organization_patch
+ toc: []
+ structuredData:
+ headings: []
+ contents:
+ - content: >
+ Patch an organization.
+
+
+ The difference between the update and patch methods is that the patch
+ will perform an update of the provided parameters, while leaving all
+ other parameters unchanged, whereas the update methods deletes all
+ parameters not explicitly provided in the data_dict.
+---
+
+{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}
+
+Patch an organization.
+
+The difference between the update and patch methods is that the patch will perform an update of the provided parameters, while leaving all other parameters unchanged, whereas the update methods deletes all parameters not explicitly provided in the data_dict.
+
+
+
\ No newline at end of file
diff --git a/docs/content/docs/package_patch.mdx b/docs/content/docs/package_patch.mdx
new file mode 100644
index 0000000..eb3c3f1
--- /dev/null
+++ b/docs/content/docs/package_patch.mdx
@@ -0,0 +1,41 @@
+---
+title: package_patch
+full: true
+_openapi:
+ method: PATCH
+ route: package_patch
+ toc: []
+ structuredData:
+ headings: []
+ contents:
+ - content: >
+ Patch a dataset (package).
+
+
+ The difference between the update and patch methods is that the patch
+ will perform an update of the provided parameters, while leaving all
+ other parameters unchanged, whereas the update methods deletes all
+ parameters not explicitly provided in the data_dict.
+
+
+ To partially update resources or other metadata not at the top level
+ of a package use `package_revise()` instead to maintain existing
+ nested values.
+
+
+ You must be authorized to edit the dataset and the groups that it
+ belongs to.
+---
+
+{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}
+
+Patch a dataset (package).
+
+The difference between the update and patch methods is that the patch will perform an update of the provided parameters, while leaving all other parameters unchanged, whereas the update methods deletes all parameters not explicitly provided in the data_dict.
+
+To partially update resources or other metadata not at the top level of a package use `package_revise()` instead to maintain existing nested values.
+
+You must be authorized to edit the dataset and the groups that it belongs to.
+
+
+
\ No newline at end of file
diff --git a/docs/content/docs/resource_patch.mdx b/docs/content/docs/resource_patch.mdx
new file mode 100644
index 0000000..d16da67
--- /dev/null
+++ b/docs/content/docs/resource_patch.mdx
@@ -0,0 +1,28 @@
+---
+title: resource_patch
+full: true
+_openapi:
+ method: PATCH
+ route: resource_patch
+ toc: []
+ structuredData:
+ headings: []
+ contents:
+ - content: >
+ Patch a resource.
+
+
+ The difference between the update and patch methods is that the patch
+ will perform an update of the provided parameters, while leaving all
+ other parameters unchanged, whereas the update methods deletes all
+ parameters not explicitly provided in the data_dict.
+---
+
+{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}
+
+Patch a resource.
+
+The difference between the update and patch methods is that the patch will perform an update of the provided parameters, while leaving all other parameters unchanged, whereas the update methods deletes all parameters not explicitly provided in the data_dict.
+
+
+
\ No newline at end of file
diff --git a/docs/content/docs/user_patch.mdx b/docs/content/docs/user_patch.mdx
new file mode 100644
index 0000000..7a3f72d
--- /dev/null
+++ b/docs/content/docs/user_patch.mdx
@@ -0,0 +1,28 @@
+---
+title: user_patch
+full: true
+_openapi:
+ method: PATCH
+ route: user_patch
+ toc: []
+ structuredData:
+ headings: []
+ contents:
+ - content: >
+ Patch a user.
+
+
+ The difference between the update and patch methods is that the patch
+ will perform an update of the provided parameters, while leaving all
+ other parameters unchanged, whereas the update methods deletes all
+ parameters not explicitly provided in the data_dict.
+---
+
+{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}
+
+Patch a user.
+
+The difference between the update and patch methods is that the patch will perform an update of the provided parameters, while leaving all other parameters unchanged, whereas the update methods deletes all parameters not explicitly provided in the data_dict.
+
+
+
\ No newline at end of file