Merge branch 'main' into feat/add-PH-badge-for-sites

Author: ItzNotABug

src/routes/(init)/init/+page.svelte

@@ -111,17 +111,16 @@
             illustration: DevKeys,
             description:
                 'Introducing Dev Keys. A new Appwrite feature that lets you bypass rate limits *during local development*. No more slowdowns. No more artificial blockers. Just fast, uninterrupted building.',
-            url: '/',
+            url: '/blog/post/announcing-dev-keys',
             content: [
-                { title: 'How do Dev Keys work', url: '/blog/post/', type: 'Blog' },
                 {
-                    title: 'Improve your Appwrite developer experience with dev keys',
-                    url: '/blog/docs',
+                    title: 'Improve your Appwrite developer experience with Dev Keys',
+                    url: '/blog/post/improve-devex-dev-keys',
                     type: 'Blog'
                 },
                 {
                     title: 'Dev Keys',
-                    url: '/',
+                    url: '/docs/advanced/platform/dev-keys',
                     type: 'Docs',
                     label: 'Visit docs'
                 }
@@ -133,7 +132,7 @@
             illustration: Formats,
             description:
                 'We have added support for two new image formats in Appwrite Storage: HEIC and AVIF. This will give you more tools to manage, manipulate, and serve images the way you need.',
-            url: '/',
+            url: '/blog/post/announcing-new-image-formats',
             content: [
                 {
                     title: 'How to use AVIF in Storage',
@@ -147,7 +146,7 @@
                 },
                 {
                     title: 'New image formats',
-                    url: '/docs/',
+                    url: '/docs/products/storage/images',
                     type: 'Docs',
                     label: 'Visit docs'
                 }

src/routes/blog/post/announcing-dev-keys/+page.markdoc

@@ -0,0 +1,88 @@
+---
+layout: post
+title: "Announcing Dev Keys: faster local development without rate limits"
+description: This new feature helps you build without interruptions. Designed to keep you productive.
+date: 2025-05-21
+cover: /images/blog/dev-keys.png
+timeToRead: 6
+author: chirag-aggarwal
+category: product
+featured: false
+---
+
+You’re building, testing, tweaking. You’re in the zone. Then—bam—rate limit.
+
+We’ve all been there. Development flow interrupted by API limits meant for production traffic. But that ends now.
+
+Introducing **Dev Keys.**
+
+A new Appwrite feature that lets you bypass rate limits *during local development*. No more slowdowns. No more artificial blockers. Just fast, uninterrupted building.
+
+And they’re built specifically for you.
+
+# Built for development
+
+Appwrite has always aimed to give you the best tools to build secure, modern apps. But testing locally with production-level rate limits? That’s been a pain point for too long.
+
+Dev Keys fix that. They let you skip rate limits while developing locally, whether building APIs, wiring up the frontend, or running automated tests.
+
+It’s a simple but powerful shift resulting in fewer errors, faster feedback, and a better overall experience.
+
+And they’re not just about rate limits. Dev Keys are also a great solution for **bypassing CORS restrictions** and **hostname validation errors** during development.
+
+# Unlimited sign-in testing
+
+Building a login screen often requires testing it over and over, tweaking error messages, checking redirects, fixing small UI bugs, etc.
+
+Appwrite’s purposefully low rate limit of 10 calls per hour would make this process slow.
+
+Dev Keys lift that limit up, allowing you to test the sign-in flow as much as you need and perfect your authentication-no interruptions.
+
+# Goodbye auto-refresh rate limit
+
+Let’s say you are working on magic-link sign-in, and using a framework like Next.js, Nuxt, or SvelteKit. These frameworks would refresh the page every time you save a file, making you quickly exhaust your magic-url sign-in request rate limit.
+
+Dev Keys solves this issue, letting you auto-refresh and make requests unlimited times so you can build, tweak, and test your flows without ever running into rate limit errors.
+
+# CORS debugging made effortless
+
+CORS errors can be really annoying to deal with, especially during development in cloud-based environments like GitHub Codespaces, Gitpods, or any other platform that gives your app a random domain.
+
+But with Dev Keys, that’s not an issue anymore. Appwrite would temporarily let any host through, so you can build and test with no more CORS headaches. No more whitelisting of random domains in the console. Just plug in the Dev Key, and get back to building.
+
+# Important features
+
+- **Rate limit bypass**: Make unlimited API requests in local development or CI/CD tests without triggering limits.
+- **CORS and hostname validation bypass**: Skip restrictive CORS checks and hostname errors that usually block client-side development.
+- **Configurable expiry**: Set Dev Keys to automatically expire after a day, a week or a month.
+- **Easy integration**: Works seamlessly with Appwrite SDKs and via headers in API requests.
+
+No production misuse. No long-term security risk. Just a better development experience.
+
+# Why it matters
+
+Hitting a rate limit while testing locally isn’t just annoying, it’s disruptive. It slows development, complicates debugging, and wastes time.
+
+On top of that, during deployment **CORS issues and hostname validation errors** can halt progress unexpectedly, especially during client-side testing. Dev Keys remove those blockers so you can test and ship without interruption.
+
+Dev Keys solve this by allowing you to test at full speed, without compromising your architecture or hitting quotas meant for live apps. Your team ships faster, more confidently, and with fewer friction points.
+
+# Built with you in mind
+
+Dev Keys are designed to allow you to iterate quickly and test thoroughly. Dev Keys keep you moving, whether you’re building a new feature, integrating with an SDK, or automating test cases.
+
+And because they’re scoped and temporary by design, they stay secure and manageable in any workflow.
+
+# How to get started
+
+To create a new Dev Key, navigate to Overview > Integrations > Dev keys and click Create Dev key. You can then implement the Dev Key while initializing the Appwrite client in your app.
+
+[Visit the docs](/docs/advanced/platform/dev-keys) to learn more.
+
+# Build without limits
+
+We built Dev Keys to make your experience with Appwrite even better. Because great development tools shouldn’t get in your way, they should get out of it.
+
+Try Dev Keys today in your next project and see the difference.
+
+Available now on **Appwrite Cloud** and **self-hosted** deployments.

src/routes/blog/post/improve-devex-dev-keys/+page.markdoc

@@ -0,0 +1,124 @@
+---
+layout: post
+title: Improve your Appwrite developer experience with dev keys
+description: Learn how you can create a dev key on Appwrite and use it in a web project to improve your developer experience.
+date: 2025-05-21
+cover: /images/blog/improve-devex-dev-keys/cover.png
+timeToRead: 7
+author: aditya-oberai
+category: tutorial
+featured: false
+callToAction: true
+---
+
+When building applications with Appwrite, developers often need a way to test and debug services repeatedly over short periods. Sometimes, this can become a hassle, as Appwrite enforces strict rate limits on client apps to prevent abuse. Developers needed a way to bypass these rate limits in their test environments and CI/CD workflows to ensure the robustness of their app functionalities.
+
+And this is the exact problem **dev keys** are here to solve!
+
+# What are dev keys?
+
+Dev keys are a type of secret used by Appwrite's client SDKs. They allow the developer to bypass any rate limits enforced by Appwrite and suppress any CORS errors caused by not using a configured hostname. A developer can configure the expiration date of a dev key to any of the three preset options (1 day, 7 days, or 30 days).
+
+Dev keys should never be used in production environments, as they can make your app more susceptible to abuse and security breaches.
+
+# Try out dev keys in an app
+
+To test dev keys, I created a simple demo web app that sends 200 requests to create a new document in an Appwrite database. To set this app up, you must complete the following steps:
+
+## Step 1: Setup Appwrite project
+
+First, create an [Appwrite Cloud](https://cloud.appwrite.io) account or [self-host Appwrite 1.7](/docs/advanced/self-hosting). Create a project (which will lead you to the project overview page) and head to the **Databases** page from the left sidebar. Create a new database with the ID `testDb` and a new collection with the ID `testCollection`. Store both of these IDs for future usage. In this collection, add the following attribute:
+
+| Name | Type | Required |
+| --- | --- | --- |
+| `number` | Integer | True |
+
+Then, head to the **Settings** tab of the collection, scroll down to the **Permissions** section, and add the following permissions:
+
+|  | Create | Read | Update | Delete |
+| --- | --- | --- | --- | --- |
+| Any | False | False | False | False |
+
+Lastly, return to the project overview page, head to the **Settings** page from the left sidebar, and copy your **API endpoint** and **project ID** for future usage.
+
+## Step 2: Create web app
+
+Next up, we'll create our test app. This will require us to create two files in our working directory:
+
+- `index.html`
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Dev keys demo</title>
+</head>
+<body>
+    <h1>Dev keys demo</h1>
+    <p>Click on this button to add 200 documents to the database in less than 1 minute.</p>
+    <button type="button">Add documents</button>
+    
+    <!-- Appwrite Web SDK -->
+    <script src="https://cdn.jsdelivr.net/npm/[email protected]"></script>
+    
+    <!-- Our app's script -->
+    <script src="app.js"></script>
+</body>
+</html>
+```
+
+- `app.js`
+
+```js
+const client = new Appwrite.Client()
+    .setEndpoint('https://<REGION>.cloud.appwrite.io/v1') // Your API Endpoint
+    .setProject('<YOUR_PROJECT_ID>'); // Your project ID
+
+const database = new Appwrite.Databases(client);
+
+document.querySelector('button').addEventListener('click', async () => {
+    const promises = [];
+    for (let i = 0; i < 200; i++) {
+        const promise = database.createDocument(
+        'testDb', // Your database ID
+        'testCollection', // Your collection ID
+        Appwrite.ID.unique(),
+        { number: i + i }
+        );
+        promises.push(promise);
+        console.log('Request initiated:', i+1);
+    }
+    
+    await Promise.all(promises);
+});
+```
+
+If you open the HTML page in your browser and click on the `Add documents` button, you will notice numerous errors in the console with the HTTP code `429`, as Appwrite's rate limits allow one client to create 120 requests per minute for this API endpoint.
+
+## Step 3: Create dev key
+
+Head back to your Appwrite project. On the overview page, select the **Dev keys** tab under the Integrations section and create a new dev key. You can add whatever name and expiry date you like.
+
+![Dev key](/images/blog/improve-devex-dev-keys/dev-key.png)
+
+After creating this dev key, head to the `app.js` file and update the Appwrite client to the following:
+
+```js
+const client = new Appwrite.Client()
+    .setEndpoint('https://<REGION>.cloud.appwrite.io/v1')
+    .setProject('<YOUR_PROJECT_ID>')
+    .setDevKey('<YOUR_DEV_KEY>'); // Your dev key
+```
+
+## Step 4: Test the app
+
+Reopen the HTML page in your browser. Clicking the `Add documents` button will allow all 200 requests to execute successfully.
+
+# Next steps
+
+And with that, you have successfully tested dev keys! Learn more about Appwrite by visiting the docs and joining the Discord community.
+
+- [Appwrite dev keys docs](/docs/advanced/platform/dev-keys)
+- [Appwrite Discord server](/discord)

src/routes/changelog/(entries)/2025-05-21.markdoc

@@ -0,0 +1,16 @@
+---
+layout: changelog
+title: "Announcing Dev Keys: faster local development without rate limits"
+date: 2025-05-21
+cover: /images/changelog/2025-05-21.png
+---
+
+Introducing **Dev Keys.**
+
+A new Appwrite feature that lets you bypass rate limits *during local development*. No more slowdowns. No more artificial blockers. Just fast, uninterrupted building.
+
+And they’re built specifically for you.
+
+{% arrow_link href="/blog/post/announcing-dev-keys" %}
+Read the announcement to learn more
+{% /arrow_link %}

src/routes/docs/products/storage/images/+page.markdoc

@@ -32,7 +32,7 @@ Below you can find all the different parameters offered by the preview endpoint
 | opacity       | Set opacity for the output image. Accepts a float value between `0-1`, where `0` makes it transparent. Only works with output formats supporting alpha channels like `png`. |
 | rotation      | Rotate the output image by a degree. Accepts an integer between `-360` to `360`.                                  |
 | background    | Set a background-color. Accepts any valid hex color value without the leading `#`. Only works with output formats supporting alpha channels like `png`. |
-| output        | Set the output image format. If not provided, will use the original image's format. Supported formats are: `jpg`, `jpeg`, `png`, `gif`, and `webp` |
+| output        | Set the output image format. If not provided, will use the original image's format. Supported formats are: `jpg`, `jpeg`, `png`, `gif`, `webp`, `avif`, and `heic` |
 
 # Examples {% #examples %}
 Here are some examples using [Client SDKs](/docs/sdks#client).