Table display of languages PoC

.claude/settings.json

@@ -0,0 +1,5 @@
+{
+  "enabledPlugins": {
+    "diataxis-documentation@deepl-claude-code-marketplace": true
+  }
+}

.github/workflows/main.yml

@@ -0,0 +1,13 @@
+on:
+  #schedule:
+  #  - cron: "0 0 * * *" # Everday at midnight
+  workflow_dispatch:
+
+jobs:
+  remove-stale-branches:
+    name: Remove Stale Branches
+    runs-on: ubuntu-latest
+    steps:
+      - uses: fpicalausa/remove-stale-branches@v2.4.0
+        with:
+          dry-run: true # Check out the console output before setting this to false

.gitignore

@@ -1 +1,5 @@
-.idea/*
+.idea/*
+reviews/*
+.DS_Store
+.DS_Store?
+.tool-versions

.mintignore

@@ -0,0 +1 @@
+reviews/*

README.md

@@ -1,14 +1,8 @@
 # DeepL Developer Docs
 
-Click on `Use this template` to copy the Mintlify starter kit. The starter kit contains examples including
+This repo is home to the [DeepL Developer Docs](https://developers.deepl.com/).
 
-- Guide pages
-- Navigation
-- Customizations
-- API Reference pages
-- Use of popular components
-
-### Development
+## Development
 
 Install the [Mintlify CLI](https://www.npmjs.com/package/mintlify) to preview the documentation changes locally. To install, use the following command
 
@@ -22,11 +16,79 @@ Run the following command at the root of your documentation (where docs.json is)
 mintlify dev
 ```
 
+It may take you directly to `localhost:3000` which has no content. Nav to `http://localhost:3000/docs/getting-started/intro` to see our docs page. 
+
 ### Publishing Changes
 
 Install our Github App to auto propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.
 
 #### Troubleshooting
 
 - Mintlify dev isn't running - Run `mintlify install` it'll re-install dependencies.
-- Page loads as a 404 - Make sure you are running in a folder with `docs.json`
+- Page loads as a 404 - Make sure you are running in a folder with `docs.json`
+
+## AI Workflow
+
+### Setting Up the DeepL Claude Code Marketplace (DeepL Internal Only)
+
+**DeepL team members:** Install our internal Claude Code marketplace to access the `diataxis-documentation` plugin for structured technical writing:
+
+1. **Add the marketplace:**
+```
+/plugin marketplace add https://git.deepl.dev/deepl/devex/ai-tooling/claude-code-marketplace.git
+```
+
+2. **Install the diataxis-documentation plugin:**
+```
+/plugin install diataxis-documentation@deepl-claude-code-marketplace
+```
+
+This gives you access to the Diátaxis framework for creating tutorials, how-to guides, references, and explanations.
+
+**The skill activates automatically** when you ask Claude to:
+- "write documentation", "create tutorial", "create guide"
+- "write how-to", "document this", "add documentation"
+- "review documentation", "improve docs", "check documentation quality"
+- Mention "technical writing", "reference docs", "explanation"
+
+When creating new documentation, the skill will:
+1. Help identify the correct documentation type (tutorial, how-to, reference, or explanation)
+2. Guide you through following Diátaxis writing principles
+3. Provide examples of good documentation structure
+
+### Subagents (Available to Everyone)
+
+We have a custom subagent in `.claude/agents/` that is **automatically available to anyone** who clones this repo (no installation required):
+
+- **`docs-reviewer.md`**: Designed to help edit our docs. Based on a sub-agent created by a GCP technical writer. (Read more in [this article](https://medium.com/google-cloud/supercharge-tech-writing-with-claude-code-subagents-and-agent-skills-44eb43e5a9b7), or [this repo](https://github.com/kazunori279/gcp-blogs/blob/main/.claude/agents/docs-reviewer.md).)
+
+### Recommended Documentation Review Workflow
+
+For the highest quality documentation, use both the diataxis plugin and docs-reviewer subagent together:
+
+1. **Write or update documentation** - Simply ask Claude naturally:
+   - "Create a tutorial for [feature]"
+   - "Write a how-to guide for [task]"
+   - "Document this API endpoint"
+
+   The diataxis skill will activate automatically and ensure your content follows the correct documentation type (tutorial, how-to, reference, or explanation).
+
+   If you prefer to write the documentation by hand, you can also say "Review this documentation".
+
+2. **Review with the docs-reviewer subagent:**
+   ```
+   Use the docs-reviewer subagent on [filename]
+   ```
+   This checks for style, clarity, and consistency with our documentation standards.
+
+This two-pass approach ensures both structural correctness (via diataxis) and editorial quality (via docs-reviewer).
+
+3. **Check for broken links:**
+
+Finally, you can run `mint broken-links` and `mint broken-links --check-anchors` to ensure all links are correct.
+
+### Future Plans
+
+- Add a subagent to search our codebase and backstage
+- Further customize subagents to match our writing style
+

analytics.js

@@ -18,6 +18,9 @@ class AnalyticsTracker {
   static EVENT_ID_NETWORK_REQUEST = 5000;
   static EVENT_ID_SEARCH_INPUT = 5001; // TODO change this after DAP update
 
+  static CONSENT_KEY = 'deepl_cookie_consent';
+  static CONSENT_ACCEPTED = 'accepted';
+
   static isProdStage = window.location.hostname === "developers.deepl.com";
   static statisticsUrl = this.isProdStage ? 
     "https://s.deepl.com/web/statistics"
@@ -149,7 +152,7 @@ class AnalyticsTracker {
         // console.log('Fetched data: ', data);
         return data;
       } catch (error) {
-        console.error('Fetch error: ', error);
+        console.error('[Analytics] Fetch error: ', error);
       }
     }
 
@@ -377,10 +380,25 @@ class AnalyticsTracker {
     }
   };
 
+  // ========================
+  //   Consent Checker
+  // ========================
+  static hasConsent() {
+    // Check localStorage for consent
+    return localStorage.getItem(this.CONSENT_KEY) === this.CONSENT_ACCEPTED;
+  }
+
   // ========================
   //   Initialization
   // ========================
   static init() {
+    // Only initialize analytics if user has consented
+    if (!this.hasConsent()) {
+      console.log('[Analytics] User has not consented to tracking. Analytics disabled.');
+      return;
+    }
+
+    console.log('[Analytics] User consent verified. Initializing analytics...');
     this.PageNavigationTracker.setupNavigationTrackers();
     this.NetworkRequestTracker.setupNetworkRequestTracking();
     // this.SearchInputTracker.setupSearchInputTracking(); // Disable this for now

api-reference/admin-api/get-usage-analytics.mdx

@@ -0,0 +1,5 @@
+---
+openapi: get /v2/admin/analytics
+title: "Get usage analytics"
+---
+

api-reference/admin-api/organization-usage-analytics.mdx

@@ -0,0 +1,54 @@
+---
+title: "Accessing organization usage analytics"
+description: "Learn how admins can retrieve and analyze usage data across their organization."
+public: true
+---
+
+The Admin API allows admins to retrieve detailed usage statistics for their organization through the [Get usage analytics](/api-reference/admin-api/get-usage-analytics) endpoint.
+
+This analytics functionality enables you to:
+* Track character usage across your entire organization
+* Monitor usage by individual API keys
+* Analyze usage patterns over time
+* Generate reports for specific date ranges
+* Break down usage by service type (text translation, document translation, text improvement)
+
+## Usage statistics endpoint
+
+The analytics endpoint provides detailed usage information for a specified date range with flexible grouping options.
+
+### Date range queries
+
+Retrieve usage statistics by specifying a start and end date. Both `start_date` and `end_date` parameters are required and support the following formats (all in UTC):
+* `YYYY-MM-DD` - Simple date format (e.g., `2025-09-29`)
+* `YYYY-MM-DDTHH:MM:SS` - Full datetime format (e.g., `2025-09-29T14:30:00`)
+
+The maximum date range is 366 days.
+
+### Grouping options
+
+The optional `group_by` parameter allows you to organize usage data in different ways:
+
+* **No grouping** (default): Returns total usage for the entire date range across all API keys
+* **`key`**: Groups usage by individual API key, showing totals for each key over the entire date range
+* **`key_and_day`**: Groups usage by both API key and day, providing daily breakdowns for each key
+
+### Usage breakdown
+
+All responses include a breakdown of usage by service type:
+* **Total characters**: Combined usage across all services
+* **Text translation characters**: Characters used for text translation
+* **Document translation characters**: Characters used for document translation
+* **Text improvement characters**: Characters used for text improvement (rephrasing)
+* **Speech-to-text minutes**: Duration of speech-to-text usage in minutes
+
+## Use cases
+
+The account-level analytics endpoint is particularly useful for:
+
+* **Cost monitoring**: Track usage to stay within budget limits and forecast costs
+* **Resource allocation**: Identify which teams or projects (represented by API keys) are using the most resources
+* **Usage trends**: Analyze daily or weekly usage patterns to optimize resource planning
+* **Compliance and auditing**: Generate detailed usage reports for compliance requirements
+* **Performance tracking**: Monitor adoption and usage of different DeepL services within your organization
+