[Fundamentals] Changelog + AOT edits

src/content/changelogs/fundamentals.yaml

@@ -0,0 +1,31 @@
+---
+link: "/fundamentals/changelog/"
+productName: Cloudflare Fundamentals
+productLink: "/fundamentals/"
+productArea: Core platform
+productAreaLink: /fundamentals/reference/changelog/platform/
+entries:
+  - publish_date: "2024-12-06"
+    title: Dashboard SCIM is now fully self-serve
+    description: |-
+      Dashboard SCIM is now self-serve. Previously, users configuring SCIM required assistance from Cloudflare to configure SCIM to onboard users. Now, with account owned tokens, SCIM can be configured by Enterprise customers that use Okta or Microsoft Entra without any assistance from Cloudflare. 
+
+      Refer to the [SCIM documentation](fundamentals/setup/account/account-security/scim-setup/) for more details.  
+  - publish_date: "2024-09-26"
+    title: Account owned tokens
+    description: |-
+      Account owned tokens are now generally available. Unlike user-owned tokens, account owned tokens are tied with the Cloudflare account instead of the user that created them. This ensures that long term integrations like CI/CD are not broken if the user that set it up leaves your organization. 
+
+      Refer to the [Account owned tokens documentation](/fundamentals/api/get-started/account-owned-tokens/) or the [blog post]( https://blog.cloudflare.com/account-owned-tokens-automated-actions-zaraz/) for more details.  
+  - publish_date: "2024-09-24"
+    title: Terraform v5 SDK Preview
+    description: |-
+      The Terraform v5 Provider is now available as a preview. This new provider is automatically generated based on the OpenAPI Specifications for our REST API, and provides improved user experiences overall. 
+
+      Refer to the [Terraform documentation](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade) or the [blog post](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more details. 
+  - publish_date: "2024-09-24"
+    title: API Documentation Preview
+    description: |-
+      Cloudflare's API documentation is now [available in preview](https://developers.cloudflare.com/api-next/) with new automatically generated documentation. This documentation includes code snippets that refer to language specific SDKs to make it easier to get started than ever. 
+
+      Refer to the [blog post](https://blog.cloudflare.com/automatically-generating-cloudflares-terraform-provider/) for more details.

src/content/docs/fundamentals/api/get-started/account-owned-tokens.mdx

@@ -1,5 +1,5 @@
 ---
-title: Account Owned Tokens
+title: Account owned tokens
 pcx_content_type: how-to
 sidebar:
   order: 6

src/content/docs/fundamentals/changelog.mdx

@@ -0,0 +1,14 @@
+---
+pcx_content_type: changelog
+title: Changelog
+changelog_file_name:
+  - fundamentals
+sidebar:
+  order: 8
+---
+
+import { ProductChangelog } from "~/components";
+
+{/* <!-- Actual content lives in /src/content/changelogs/fundamentals.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
+
+<ProductChangelog />

src/content/docs/fundamentals/reference/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: navigation
 title: Reference
 sidebar:
-  order: 8
+  order: 7
   group:
     hideIndex: true
 head:

src/content/docs/fundamentals/setup/account/account-security/scim-setup.mdx

@@ -38,7 +38,7 @@ Accounts provisioned with SCIM need to verify their email addresses.
 
    :::note
 
-   Cloudflare recommends using Account Owned API Tokens for SCIM Provisioning. Using user-specific API tokens, while supported, will lead to a broken SCIM connection in the event that the user's policies are revoked from the account with the SCIM integration. Learn more about [Account Owned Tokens](/fundamentals/api/get-started/account-owned-tokens/).
+   Cloudflare recommends using Account Owned API Tokens for SCIM Provisioning. Using user-specific API tokens, while supported, will lead to a broken SCIM connection in the event that the user's policies are revoked from the account with the SCIM integration. Learn more about [account owned tokens](/fundamentals/api/get-started/account-owned-tokens/).
    :::
 
 2. Under **Account Resources**, select the specific account to include or exclude from the dropdown menu, if applicable.

src/content/partials/fundamentals/account-owned-tokens.mdx

@@ -4,28 +4,28 @@
 
 ---
 
-Account Owned Tokens are the first step that Cloudflare is taking to represent service principals in our service.
+Account owned tokens are the first step that Cloudflare is taking to represent service principals in our service.
 
-Cloudflare is working to ensure that all features eventually become compatible with Account Owned Tokens. 
+Cloudflare is working to ensure that all features eventually become compatible with account owned tokens. 
 
-If you are working with a service that is not currently supported by Account Owned Tokens, it is recommended that you continue to use the existing user tokens.
+If you are working with a service that is not currently supported by account owned tokens, it is recommended that you continue to use the existing user tokens.
 
 :::note
 User tokens will continue to work and we do not have plans to deprecate them.
 :::
 
-Account Owned Tokens are available to all customers. Super Administrators of accounts on the [Cloudflare dashboard](https://dash.cloudflare.com/) can find them via **Manage Account** > **API Tokens**.
+Account owned tokens are available to all customers. Super Administrators of accounts on the [Cloudflare dashboard](https://dash.cloudflare.com/) can find them via **Manage Account** > **API Tokens**.
 
 You can still create tokens using the Cloudflare dashboard, and it can also be accessed via the API at `/accounts/<accountID>/tokens`.
 
-Try using Account Owned Tokens specifically in these scenarios:
+Try using account owned tokens specifically in these scenarios:
 
 - You require business continuity when managing tokens as a team of super administrators.
 - You need to restrict API access on your account and want to centralize visibility and management of these tokens.
 
 ## Compatibility matrix
 
-Account Owned Tokens are a new credential type that is currently in open beta. Refer to the table below for products currently supported and their compatibility status.
+Account owned tokens are a new credential type that is currently in open beta. Refer to the table below for products currently supported and their compatibility status.
 
 | Product                         | Compatible              |
 | ------------------------------- | ----------------------- |

src/content/partials/fundamentals/create-token.mdx

@@ -13,7 +13,7 @@ Before you begin, [find your zone and account IDs](/fundamentals/setup/find-acco
 
 :::
 
-1. Determine if you want a user token or an [Account Owned Token](/fundamentals/api/get-started/account-owned-tokens/). Use Account Owned Tokens if you prefer service tokens that are not associated with users and your [desired API endpoints are compatible](/fundamentals/api/get-started/account-owned-tokens/#compatibility-matrix).
+1. Determine if you want a user token or an [Account owned token](/fundamentals/api/get-started/account-owned-tokens/). Use Account owned tokens if you prefer service tokens that are not associated with users and your [desired API endpoints are compatible](/fundamentals/api/get-started/account-owned-tokens/#compatibility-matrix).
 
 2. From the [Cloudflare dashboard](https://dash.cloudflare.com/profile/api-tokens/), go to **My Profile** > **API Tokens** for user tokens. For Account Tokens, go to **Manage Account** > **API Tokens**.