Random aria IDs #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

sofyanori111-png wants to merge 35 commits into production from accessibiilty-fixes-2

.github/CODEOWNERS

-Original file line number
+Diff line change
@@ Expand Up / @@ -26,13 +26,19 @@ @@
     # Developer platform
     /content/d1/ @elithrar @rozenmd @cloudflare/pcx-technical-writing
+    /data/changelogs/d1.yaml @elithrar @rozenmd @cloudflare/pcx-technical-writing
     /content/images/ @GregBrimble @cloudflare/pcx-technical-writing
     /content/pages/ @cloudflare/workers-docs @GregBrimble @WalshyDev @cloudflare/pcx-technical-writing
+    /data/changelogs/pages.yaml @cloudflare/workers-docs @GregBrimble @WalshyDev @cloudflare/pcx-technical-writing
     /content/pub-sub/ @CharlieBurnett @elithrar @cloudflare/pcx-technical-writing
     /content/queues/ @CharlieBurnett @elithrar @cloudflare/pcx-technical-writing
+    /data/changelogs/queues.yaml @CharlieBurnett @elithrar @cloudflare/pcx-technical-writing
     /content/r2/ @cloudflare/workers-docs @cloudflare/pcx-technical-writing
+    /data/changelogs/r2.yaml @cloudflare/workers-docs @cloudflare/pcx-technical-writing
     /content/stream/ @tsmith512 @cloudflare/pcx-technical-writing
+    /data/changelogs/stream.yaml @tsmith512 @cloudflare/pcx-technical-writing
     /content/workers/ @cloudflare/workers-docs @GregBrimble @WalshyDev @cloudflare/pcx-technical-writing
+    /data/changelogs/workers.yaml @cloudflare/workers-docs @GregBrimble @WalshyDev @cloudflare/pcx-technical-writing
     /content/zaraz/ @bjesus @cloudflare/pcx-technical-writing
     /content/workers/runtime-apis/ @irvinebroque @jasnell @cloudflare/pcx-technical-writing
     /content/workers/configuration/bindings/ @irvinebroque @cloudflare/pcx-technical-writing
@@ Expand Down @@

config.toml

-Original file line number
+Diff line change
@@ Expand Up / @@ -21,10 +21,14 @@ org = "cloudflareproduction7iy98g48" @@
     token = "xx2b20a6dc-ce86-41cb-ad18-90bd2568dcdb"
     tutorial_token = "xxa5a7d4c9-db72-424d-860d-ae68ff7f60ac"
+    [outputs]
+      home = ['html']
+      page = ['html']
+      section = ['html']
     [sitemap]
-      changefreq = "daily"
+      changefreq = "weekly"
       filename = "sitemap.xml"
-      priority = 0.7
     [markup]
     	[markup.goldmark]
@@ Expand Down @@

content/_index.html

-Original file line number
+Diff line change
@@ Expand Up / @@ -25,7 +25,7 @@ @@
     </div>
     <div>
     {{<quad-block>}}
-      [Cloudflare Status](https://www.cloudflarestatus.com/)
+      [Changelog](/changelog/)
     {{</quad-block>}}
     </div>
     </div>
@@ Expand Down @@

content/changelog.html

-Original file line number
+Diff line change
@@ -0,0 +1,19 @@
+    ---
+    title: Changelog
+    type: developers-site
+    layout: home
+    outputs:
+        - html
+        - rss
+    meta:
+      description: View updates to various Cloudflare products.
+    ---
+    <div class="Stripe">
+      <div class="Stripe--content">
+        <h1 id="documentation">Changelog</h1>
+        <p id="description">Subscribe to all Changelog posts via <a class="rssLink" href="/changelog/index.xml">RSS</a>.</p>
+      </div>
+    </div>
+    {{<full-changelog>}}

content/d1/changelog.md

-Original file line number
+Diff line change
@@ Expand Up / @@ -2,109 +2,15 @@ @@
     pcx_content_type: changelog
     title: Changelog
     weight: 11
-    rss: file
+    layout: changelog
+    changelog_file_name: d1
+    outputs:
+        - html
+        - rss
     ---
     # Changelog
-    ## 2023-08-19
+    <!-- Actual content lives in /data/changelogs/d1.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 -->
-    ### Row count now returned per query
-    D1 now returns a count of `rows_written` and `rows_read` for every query executed, allowing you to assess the cost of query for both [pricing](/d1/platform/pricing/) and [index optimization](/d1/learning/using-indexes/) purposes.
-    The `meta` object returned in [D1's Client API](/d1/platform/client-api/) contains a total count of the rows read (`rows_read`) and rows written (`rows_written`) by that query. For example, a query that performs a full table scan (for example, `SELECT * FROM users`) from a table with 5000 rows would return a `rows_read` value of `5000`:
-    ```json
-    "meta": {
-      "duration": 0.20472300052642825,
-      "size_after": 45137920,
-      "rows_read": 5000,
-      "rows_written": 0
-    }
-    ```
-    Refer to [D1 pricing documentation](/d1/platform/pricing/) to understand how reads and writes are measured. D1 remains free to use during the alpha period.
-    ## 2023-08-09
-    ### Bind D1 from the Cloudflare dashboard
-    You can now [bind a D1 database](/d1/get-started/#3-bind-your-worker-to-your-d1-database) to your Workers directly in the [Cloudflare dashboard](https://dash.cloudflare.com). To bind D1 from the Cloudflare dashboard, select your Worker project -> **Settings** -> **Variables** -> and select **D1 Database Bindings**.
-    Note: If you have previously deployed a Worker with a D1 database binding with a version of `wrangler` prior to `3.5.0`, you must upgrade to [`wrangler v3.5.0`](https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.5.0) first before you can edit your D1 database bindings in the Cloudflare dashboard. New Workers projects do not have this limitation.
-    Legacy D1 alpha users who had previously prefixed their database binding manually with `__D1_BETA__` should remove this as part of this upgrade. Your Worker scripts should call your D1 database via `env.BINDING_NAME` only. Refer to the latest [D1 getting started guide](/d1/get-started/#3-bind-your-worker-to-your-d1-database) for best practices.
-    We recommend all D1 alpha users begin using wrangler `3.5.0` (or later) to benefit from improved TypeScript types and future D1 API improvements.
-    ## 2023-08-01
-    ### Per-database limit now 500 MB
-    Databases using D1's [new storage subsystem](/d1/changelog/#new-default-storage-subsystem) can now grow to 500 MB each, up from the previous 100 MB limit. This applies to both existing and newly created databases.
-    Refer to [Limits](/d1/platform/limits/) to learn about D1's limits.
-    ## 2023-07-27
-    ### New default storage subsystem
-    Databases created via the Cloudflare dashboard and Wrangler (as of `v3.4.0`) now use D1's new storage subsystem by default. The new backend can [be 6 - 20x faster](https://blog.cloudflare.com/d1-turning-it-up-to-11/) than D1's original alpha backend.
-    To understand which storage subsystem your database uses, run `wrangler d1 info YOUR_DATABASE` and inspect the version field in the output.
-    Databases with `version: beta` use the new storage backend and support the [Time Travel](/d1/learning/time-travel/) API. Databases with `version: alpha` only use D1's older, legacy backend.
-    ### Time Travel
-    [Time Travel](/d1/learning/time-travel/) is now available. Time Travel allows you to restore a D1 database back to any minute within the last 30 days (Workers Paid plan) or 7 days (Workers Free plan), at no additional cost for storage or restore operations.
-    Refer to the [Time Travel](/d1/learning/time-travel/) documentation to learn how to travel backwards in time.
-    Databases using D1's [new storage subsystem](https://blog.cloudflare.com/d1-turning-it-up-to-11/) can use Time Travel. Time Travel replaces the [snapshot-based backups](/d1/learning/backups/) used for legacy alpha databases.
-    ## 2023-06-28
-    ### Metrics and analytics
-    You can now view [per-database metrics](/d1/platform/metrics-analytics/) via both the [Cloudflare dashboard](https://dash.cloudflare.com/) and the [GraphQL Analytics API](/analytics/graphql-api/).
-    D1 currently exposes read & writes per second, query response size, and query latency percentiles.
-    ## 2023-06-16
-    ### Generated columns documentation
-    New documentation has been published on how to use D1's support for [generated columns](/d1/learning/generated-columns/) to define columns that are dynamically generated on write (or read). Generated columns allow you to extract data from [JSON objects](/d1/learning/querying-json/) or use the output of other SQL functions.
-    ## 2023-06-12
-    ### Deprecating Error.cause
-    As of [`wrangler v3.1.1`](https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.1.1) the [D1 client API](/d1/platform/client-api/) now returns [detailed error messages](/d1/platform/client-api/#errors) within the top-level `Error.message` property, and no longer requires developers to inspect the `Error.cause.message` property.
-    To facilitate a transition from the previous `Error.cause` behaviour, detailed error messages will continue to be populated within `Error.cause` as well as the top-level `Error` object until approximately July 14th, 2023. Future versions of both `wrangler` and the D1 client API will no longer populate `Error.cause` after this date.
-    ## 2023-05-19
-    ### New experimental backend
-    D1 has a new experimental storage back end that dramatically improves query throughput, latency and reliability. The experimental back end will become the default back end in the near future. To create a database using the experimental backend, use `wrangler` and set the `--experimental-backend` flag when creating a database:
-    ```sh
-    $ wrangler d1 create your-database --experimental-backend
-    ```
-    Read more about the experimental back end in the [announcement blog](https://blog.cloudflare.com/d1-turning-it-up-to-11/).
-    ### Location hints
-    You can now provide a [location hint](/d1/learning/data-location/) when creating a D1 database, which will influence where the leader (writer) is located. By default, D1 will automatically create your database in a location close to where you issued the request to create a database. In most cases this allows D1 to choose the optimal location for your database on your behalf.
-    ## 2023-05-17
-    ### Query JSON
-    [New documentation](/d1/learning/querying-json/) has been published that covers D1's extensive JSON function support. JSON functions allow you to parse, query and modify JSON directly from your SQL queries, reducing the number of round trips to your database, or data queried.
+    {{<product-changelog>}}

content/pages/platform/changelog.md

-Original file line number
+Diff line change
@@ -1,96 +1,15 @@
     ---
     pcx_content_type: changelog
     title: Changelog
-    rss: file
+    layout: changelog
+    changelog_file_name: pages
+    outputs:
+        - html
+        - rss
     ---
     # Changelog
-    ## 2023-02-14
+    <!-- Actual content lives in /data/changelogs/pages.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 -->
-    * Added support for [Analytics Engine](/analytics/analytics-engine/) in Functions.
-    ## 2023-01-05
-    * Added support for [Queues](/queues/) producer in Functions.
-    ## 2022-12-15
-    * Updated all API messaging to be more helpful.
-    ## 2022-12-01
-    * Aliased deployments can now be deleted.
-      * If using the API, you will need to add the query parameter `force=true`.
-    ## 2022-11-19
-    * You can now deep-link to a Pages deployment in the dashboard with `:pages-deployment`.
-      * Example: `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment`.
-    ## 2022-11-17
-    * Functions GA
-      * Blog post: https://blog.cloudflare.com/pages-function-goes-ga/
-    * Functions metrics are now available in the dashboard.
-      * You can [view them here](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/analytics/production).
-    * Functions billing is now available.
-      * You can [view details here](/pages/platform/functions/pricing).
-    * The [Unbound usage model](/workers/platform/limits/#response-limits) is now available for Functions.
-    * [Secrets](/pages/platform/functions/bindings/#secrets) are now available.
-    * Functions tailing is now available.
-      * You can tail within the dash here: https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions.
-      * Or with Wrangler - `wrangler pages deployment tail`.
-    ## 2022-11-15
-    * Service bindings are now available in Functions.
-      * [Documentation available here](/pages/platform/functions/bindings/#service-bindings).
-    ## 2022-11-03
-    * Build log now supports ansi color codes.
-    ## 2022-10-05
-    * You can now deep-link to a Pages project in the dashboard with `:pages-project`.
-      * Example: `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project`.
-    ## 2022-09-12
-    * Increased domain limits.
-      * Before increase, all plans had a maximum of 10 custom domains per project.
-      * New limits:
-        * Free - 100 custom domains
-        * Pro - 250 custom domains
-        * Business/Enterprise - 500 custom domains
-    ## 2022-09-08
-    * Support `_routes.json`.
-      * Documentation [available here](/pages/platform/functions/routing/#functions-invocation-routes).
-    ## 2022-08-25
-    * Build log expiration time increased from 2 weeks to 1 year.
-    ## 2022-08-08
-    * R2 and D1 bindings are now supported.
-    ## 2022-07-05
-    * Added support for `.dev.vars` in `wrangler pages`.
-      * This allows you to use environmental variables during your local development without chaining `--env`s.
-      * Requires Wrangler v2.0.16 or higher.
-    ## 2022-06-13
-    * Added deltas to `wrangler pages publish`.
-      * We now keep track of the files that make up each deployment and intelligently only upload the files that we have not seen. This means that similar subsequent deployments should only need to upload a minority of files and this will hopefully make uploads even faster.
-      * Requires Wrangler v2.0.11 or higher.
-    ## 2022-06-08
-    * Added branch alias in PR comments.
-    ![Branch alias in PR comment](/images/pages/platform/branch_alias_pr_comment.png)
+    {{<product-changelog>}}

content/queues/changelog.md

-Original file line number
+Diff line change
@@ -1,50 +1,15 @@
     ---
     pcx_content_type: changelog
     title: Changelog
-    weight: 11
-    rss: file
+    layout: changelog
+    changelog_file_name: queues
+    outputs:
+        - html
+        - rss
     ---
     # Changelog
-    ## 2023-03-28
+    <!-- Actual content lives in /data/changelogs/queues.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 -->
-    ### Consumer concurrency (enabled)
-    Queue consumers will now [automatically scale up](/queues/learning/consumer-concurrency/) based on the number of messages being written to the queue. To control or limit concurrency, you can explicitly define a [`max_concurrency`](/queues/platform/configuration/#consumer) for your consumer.
-    ## 2023-03-15
-    ### Consumer concurrency (upcoming)
-    Queue consumers will soon automatically scale up concurrently as a queues' backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.
-    **To opt-out, or to configure a fixed maximum concurrency**, set `max_concurrency = 1` in your `wrangler.toml` file or via [the queues dashboard](https://dash.cloudflare.com/?to=/:account/queues).
-    **To opt-in, you do not need to take any action**: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the [consumer concurrency](/queues/learning/consumer-concurrency/) documentation.
-    ## 2023-03-02
-    ### Explicit acknowledgement (new feature)
-    You can now [acknowledge individual messages with a batch](/queues/learning/batching-retries/#explicit-acknowledgement) by calling `.ack()` on a message.
-    This allows you to mark a message as delivered as you process it within a batch, and avoids the entire batch from being redelivered if your consumer throws an error during batch processing. This can be particularly useful when you are calling external APIs, writing messages to a database, or otherwise performing non-idempotent actions on individual messages within a batch.
-    ## 2023-03-01
-    ### Higher per-queue throughput
-    The per-queue throughput limit has now been [raised to 400 messages per second](/queues/platform/limits/).
-    ## 2022-12-12
-    ### Increased per-account limits
-    Queues now allows developers to create up to 100 queues per account, up from the initial beta limit of 10 per account. This limit will continue to increase over time.
-    ## 2022-12-13
-    ### sendBatch support
-    The JavaScript API for Queue producers now includes a `sendBatch` method which supports sending up to 100 messages at a time.
+    {{<product-changelog>}}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Random aria IDs #1

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!

Random aria IDs #1

Are you sure you want to change the base?

Uh oh!

Random aria IDs #1

Uh oh!

Uh oh!

Diff view

Diff view

There are no files selected for viewing

Uh oh!