👻Delete useless files

23 files changed, 23 insertions, 283 deletions

diff --git a/docs/pages/AI/_meta.json b/docs/pages/MODEL/_meta.json
index 4941080..4941080 100644
--- a/docs/pages/AI/_meta.json
+++ b/docs/pages/MODEL/_meta.json
diff --git a/docs/pages/AI/docs/_meta.json b/docs/pages/MODEL/docs/_meta.json
index 939e2df..939e2df 100644
--- a/docs/pages/AI/docs/_meta.json
+++ b/docs/pages/MODEL/docs/_meta.json
diff --git a/docs/pages/AI/docs/acknowledgements.mdx b/docs/pages/MODEL/docs/acknowledgements.mdx
index 50a5c46..50a5c46 100644
--- a/docs/pages/AI/docs/acknowledgements.mdx
+++ b/docs/pages/MODEL/docs/acknowledgements.mdx
diff --git a/docs/pages/AI/docs/faq.mdx b/docs/pages/MODEL/docs/faq.mdx
index 6039dae..6039dae 100644
--- a/docs/pages/AI/docs/faq.mdx
+++ b/docs/pages/MODEL/docs/faq.mdx
diff --git a/docs/pages/AI/docs/getting-started/_meta.json b/docs/pages/MODEL/docs/getting-started/_meta.json
index 2ed5b29..2ed5b29 100644
--- a/docs/pages/AI/docs/getting-started/_meta.json
+++ b/docs/pages/MODEL/docs/getting-started/_meta.json
diff --git a/docs/pages/AI/docs/getting-started/add-to-project.mdx b/docs/pages/MODEL/docs/getting-started/add-to-project.mdx
index 7f7ecec..7f7ecec 100644
--- a/docs/pages/AI/docs/getting-started/add-to-project.mdx
+++ b/docs/pages/MODEL/docs/getting-started/add-to-project.mdx
diff --git a/docs/pages/AI/docs/getting-started/create-new.mdx b/docs/pages/MODEL/docs/getting-started/create-new.mdx
index aa16eb4..aa16eb4 100644
--- a/docs/pages/AI/docs/getting-started/create-new.mdx
+++ b/docs/pages/MODEL/docs/getting-started/create-new.mdx
diff --git a/docs/pages/AI/docs/getting-started/existing-monorepo.mdx b/docs/pages/MODEL/docs/getting-started/existing-monorepo.mdx
index 3f81530..3f81530 100644
--- a/docs/pages/AI/docs/getting-started/existing-monorepo.mdx
+++ b/docs/pages/MODEL/docs/getting-started/existing-monorepo.mdx
diff --git a/docs/pages/AI/docs/getting-started/from-example.mdx b/docs/pages/MODEL/docs/getting-started/from-example.mdx
index 6b35768..6b35768 100644
--- a/docs/pages/AI/docs/getting-started/from-example.mdx
+++ b/docs/pages/MODEL/docs/getting-started/from-example.mdx
diff --git a/docs/pages/AI/docs/index.mdx b/docs/pages/MODEL/docs/index.mdx
index 5f6dd29..5f6dd29 100644
--- a/docs/pages/AI/docs/index.mdx
+++ b/docs/pages/MODEL/docs/index.mdx
diff --git a/docs/pages/AI/docs/installing.mdx b/docs/pages/MODEL/docs/installing.mdx
index 265b3b1..265b3b1 100644
--- a/docs/pages/AI/docs/installing.mdx
+++ b/docs/pages/MODEL/docs/installing.mdx
diff --git a/docs/pages/AI/docs/troubleshooting.mdx b/docs/pages/MODEL/docs/troubleshooting.mdx
index 3fba847..3fba847 100644
--- a/docs/pages/AI/docs/troubleshooting.mdx
+++ b/docs/pages/MODEL/docs/troubleshooting.mdx
diff --git a/docs/pages/AI/index.mdx b/docs/pages/MODEL/index.mdx
index 97240f5..97240f5 100644
--- a/docs/pages/AI/index.mdx
+++ b/docs/pages/MODEL/index.mdx
diff --git a/docs/pages/TRPG/docs/_meta.json b/docs/pages/TRPG/docs/_meta.json
index 1b30674..8ffd2a5 100644
--- a/docs/pages/TRPG/docs/_meta.json
+++ b/docs/pages/TRPG/docs/_meta.json
@@ -1,6 +1,6 @@
 {
-  "index": "Quickstart",
-  "why-trpg": "Why TRPG?",
-  "core-concepts": "Core Concepts",
-  "features": "Features"
+  "index": "快速开始",
+  "why-trpg": "为什么是 TRPG跑团?",
+  "core-concepts": "核心概念",
+  "features": "特性"
 }
diff --git a/docs/pages/TRPG/docs/core-concepts.mdx b/docs/pages/TRPG/docs/core-concepts.mdx
index 9a58ab7..552dda6 100644
--- a/docs/pages/TRPG/docs/core-concepts.mdx
+++ b/docs/pages/TRPG/docs/core-concepts.mdx
@@ -1,64 +1,8 @@
 ---
-title: Core Concepts
-description: Learn about the innovative architecture that powers TRPG's speed improvements.
+title: 核心概念
+description: 了解核心
 ---
 
 # Core Concepts
 
-Let’s dive deep into the internals of TRPG to figure out why it’s so fast.
-
-## The Turbo engine
-
-TRPG is so fast because it’s built on a reusable library for Rust which enables incremental computation known as the Turbo engine. Here’s how it works:
-
-### Function-level caching
-
-In a Turbo engine-powered program, you can mark certain functions as ‘to be remembered’. When these functions are called, the Turbo engine will remember **what they were called with**, and **what they returned**. It’ll then save it in an in-memory cache.
-
-Here’s a simplified example of what this might look like in a bundler:
-
-![](/images/docs/TRPG/turbo-engine-first-run.png)
-
-We start with calling `readFile` on two files, `api.ts` and `sdk.ts`. We then `bundle` those files, `concat` them together, and end up with the `fullBundle` at the end. The results of all of those function calls get saved in the cache for later.
-
-Let’s imagine that we’re running on a dev server. You save the `sdk.ts` file on your machine. TRPG receives the file system event, and knows it needs to recompute `readFile("sdk.ts")`:
-
-![](/images/docs/TRPG/turbo-engine-second-run.png)
-
-Since the result of `sdk.ts` has changed, we need to `bundle` it again, which then needs to be concatenated again.
-
-Crucially, `api.ts` hasn’t changed. We read its result from the cache and pass that to `concat` instead. So we save time by not reading it and re-bundling it again.
-
-Now imagine this in a real bundler, with thousands of files to read and transformations to execute. The mental model is the same. You can save enormous amounts of work by remembering the result of function calls and not re-doing work that’s been done before.
-
-### The cache
-
-The Turbo engine currently stores its cache in memory. This means the cache will last as long as the process running it - which works well for a dev server. When you run `next dev --turbo` in Next v13, you’ll start a cache with the Turbo engine. When you cancel your dev server, the cache gets cleared.
-
-In the future, we’re planning to persist this cache - either to the filesystem, or to a remote cache like Turborepo’s. This will mean that TRPG could remember work done _across runs and machines._
-
-### How does it help?
-
-This approach makes TRPG extremely fast at computing incremental updates to your apps. This optimizes TRPG for handling updates in development, meaning your dev server will always respond snappily to changes.
-
-In the future, a persistent cache will open the door to much faster production builds. By remembering work done _across runs_, new production builds could only rebuild changed files - potentially leading to enormous time savings.
-
-## Compiling by Request
-
-The Turbo engine helps provide extremely fast _updates_ on your dev server, but there’s another important metric to consider - startup time. The faster your dev server can start running, the faster you can get to work.
-
-There are two ways to make a process faster - work faster, or do less work. For starting up a dev server, the way to do less work is to compile _only the code that’s needed_ to get started.
-
-### Page-level compilation
-
-Versions of Next.js from 2-3 years ago used to compile the _entire application_ before showing your dev server. In Next.js [11], we began compiling _only the code on the page you requested._
-
-That’s better, but it’s not perfect. When you navigate to `/users`, we’ll bundle all the client and server modules, dynamic-imported modules, and referenced CSS and images. That means if a large part of your page is hidden from view, or hidden behind tabs, we’ll still compile it anyway.
-
-### Request-level compilation
-
-TRPG is smart enough to compile _only the code you request_. That means if a browser requests HTML, we compile only the HTML - not anything that is referenced by the HTML.
-
-If a browser wants some CSS, we’ll compile only that - without compiling referenced images. Got a big charting library behind `next/dynamic`? Doesn’t compile it until the tab showing the chart is shown. TRPG even knows _to not compile source maps unless your Chrome DevTools are open_.
-
-If we were to use native ESM, we’d get similar behavior. Except that Native ESM produces a _lot_ of requests to the server, as discussed in our [Why TRPG](/TRPG/docs/why-TRPG) section. With request-level compilation, we get to both reduce the number of requests _and_ use native speed to compile them. As you can see in our [benchmarks](/TRPG/docs/benchmarks), this provides significant performance improvements.
+水系核心概念
\ No newline at end of file
diff --git a/docs/pages/TRPG/docs/features.mdx b/docs/pages/TRPG/docs/features.mdx
index a770c35..f069b86 100644
--- a/docs/pages/TRPG/docs/features.mdx
+++ b/docs/pages/TRPG/docs/features.mdx
@@ -1,22 +1,12 @@
 ---
-title: Features
-description: Learn about TRPG's supported features
+title: 特性
+description: 认识水系的一些特点
 ---
 
 import { HydroRollTRPGFeatures } from '../../../components/HydroRollTRPGFeatures'
 
-# Features
+# 特性
 
-The practice of building web applications is enormously diverse. In CSS alone, you have SCSS, Less, CSS Modules, PostCSS, and hundreds of other libraries. Frameworks like React, Vue and Svelte require custom setups.
-
-When building a bundler, we needed to consider which features would be:
-
-- **Built-in**: they work out of the box, no config required
-- **Available via plugins**: usually installed from a registry and configured
-- **Unavailable**: not available at all
-
-**TRPG is in alpha**, so very few of these decisions are set in stone. In its current state, **TRPG cannot yet be configured** - so plugins are not available yet.
-
-Let's discuss which features are available out-of-the-box, in TRPG's default configuration. We'll also touch on features which will be configurable via plugins.
+To be...
 
 <HydroRollTRPGFeatures />
diff --git a/docs/pages/TRPG/docs/index.mdx b/docs/pages/TRPG/docs/index.mdx
index 75308de..0a1a30f 100644
--- a/docs/pages/TRPG/docs/index.mdx
+++ b/docs/pages/TRPG/docs/index.mdx
@@ -1,6 +1,6 @@
 ---
-title: TRPG Quickstart
-description: Start Building Web Applications with TRPG
+title: TRPG 快速入门
+description: 开始搭建纯净的水系骰子
 ---
 
 import { HydroRollTRPGQuickstartArea } from "../../../components/HydroRollTRPGQuickstart";
@@ -8,53 +8,7 @@ import Callout  from "../../../components/Callout";
 import { Tabs, Tab } from "../../../components/Tabs";
 import FullTurboCTA from "../../../components/FullTurboCTA";
 
-# Getting Started with TRPG
-
-TRPG is an incremental bundler optimized for JavaScript and TypeScript, written in Rust by the creators of webpack and [Next.js](https://nextjs.org/) at [Vercel](https://vercel.com/).
-
-The secret to TRPG's performance is twofold: highly optimized machine code and a low-level incremental computation engine that enables caching down to the level of individual functions. Once TRPG performs a task it never does it again.
-
-Our team has taken the lessons from 10 years of webpack, combined with the innovations in incremental computation from [Turborepo](/repo) and Google's Bazel, and created an architecture ready to support the coming decades of computing.
-
-<Callout type="error">
-    TRPG is currently in <strong>alpha</strong>. It is not yet ready for production use. We appreciate your support and feedback as we work to make it ready for everyone.
-</Callout>
-
-## Quickstart
-
-As of today, TRPG can be used in Next.js v13. In the future we will be releasing a standalone CLI, plugin API, and support for other frameworks such as Svelte and Vue. For now, please follow these instructions to get started:
-
-1. Create a Next.js v13 project with TRPG:
-
-```bash
-npx create-next-app --example with-TRPG
-```
-
-2. Start the Next.js development server (with TRPG):
-
-  <Tabs items={["npm", "yarn", "pnpm"]} storageKey="selected-pkg-manager">
-    <Tab>
-      ```bash
-      npm run dev
-      ```
-    </Tab>
-    <Tab>
-      ```bash
-      yarn dev
-      ```
-    </Tab>
-    <Tab>
-      ```bash
-      pnpm dev
-      ```
-    </Tab>
-  </Tabs>
-
-The Next.js v13 development server is now powered by TRPG! Startup and updates should both be near-instant. The larger the application, the larger the improvement will be.
-
-## Next Steps
-
-Want to learn more about TRPG? Here's a deep dive on what we think makes it special.
+# 快速开始
 
 <HydroRollTRPGQuickstartArea />
 
diff --git a/docs/pages/TRPG/docs/why-trpg.mdx b/docs/pages/TRPG/docs/why-trpg.mdx
index 571a54f..14848e2 100644
--- a/docs/pages/TRPG/docs/why-trpg.mdx
+++ b/docs/pages/TRPG/docs/why-trpg.mdx
@@ -1,62 +1,8 @@
 ---
-title: Why TRPG?
-description: Learn why we think TRPG is the future of bundling for the web.
+title: 为什么是 TRPG跑团?
+description: 关于水系诞生的决定
 ---
 
 # Why TRPG?
 
-When we set out to create TRPG, we wanted to solve a problem. We had been working on speed improvements for Next.js. We migrated away from several JS-based tools. Babel, gone. Terser, gone. Our next target was another JS-based tool, webpack.
-
-Replacing it became our goal. But with what?
-
-A new generation of native-speed bundlers were emerging, like esbuild and swc. But after assessing the bundlers on the market, we decided to build our own. Why?
-
-## Bundling vs Native ESM
-
-Frameworks like Vite use a technique where they don’t bundle application source code in development mode. Instead, they rely on the browser’s native ES Modules system. This approach results in incredibly responsive updates since they only have to transform a single file.
-
-However, Vite can hit scaling issues with large applications made up of many modules. A flood of cascading network requests in the browser can lead to a relatively slow startup time. For the browser, it’s faster if it can receive the code it needs in as few network requests as possible - even on a local server.
-
-That’s why we decided that, like webpack, we wanted TRPG to bundle the code in the development server. TRPG can do it much faster, especially for larger applications, because it is written in Rust and skips optimization work that is only necessary for production.
-
-## Incremental Computation
-
-There are two ways to make a process faster: do less work or do work in parallel. We knew if we wanted to make the fastest bundler possible, we’d need to pull hard on both levers.
-
-We decided to create a reusable Turbo build engine for distributed and incremental behavior. The Turbo engine works like a scheduler for function calls, allowing calls to functions to be parallelized across all available cores.
-
-The Turbo engine also caches the result of all the functions it schedules, meaning it never needs to do the same work twice. Put simply, **it does the minimum work at maximum speed**.
-
-### Vite and esbuild
-
-Other tools take a different attitude to ‘doing less work’. Vite minimizes work done by using Native ESM in development mode. We decided not to take this approach for the reasons listed above.
-
-Under the hood, Vite uses esbuild for many tasks. esbuild is a bundler - a superbly fast one. It doesn’t force you to use native ESM. But we decided not to adopt esbuild for a few reasons.
-
-esbuild’s code is hyper-optimized for one task - bundling fast. It doesn’t have HMR, which we don’t want to lose from our dev server.
-
-esbuild is an extremely fast bundler, but it doesn’t do much caching. This means you _will_ end up doing the same work again and again, even if that work is at the speed of native.
-
-Evan Wallace refers to esbuild as a [proof-of-concept for the next generation of bundlers](https://news.ycombinator.com/item?id=22336334). We think he’s right. We feel that a Rust-powered bundler _with_ incremental computation could perform better at a larger scale than esbuild.
-
-## Lazy bundling
-
-Early versions of Next.js tried to bundle the _entire_ web app in development mode. We quickly realized that this ‘eager’ approach was less than optimal. Modern versions of Next.js bundle only the pages requested by the dev server. For instance, if you go to `localhost:3000`, it’ll bundle only `pages/index.jsx`, and the modules it imports.
-
-This more ‘lazy’ approach (only bundling assets when absolutely necessary) is key for a fast dev server. Native ESM handles this without much magic - you request a module, which requests other modules. However, we wanted to build a bundler, for the reasons explained above.
-
-esbuild doesn’t have a concept of ‘lazy’ bundling - it’s all-or-nothing, unless you specifically target only certain entry points.
-
-TRPG’s development mode builds a minimal graph of your app’s imports and exports based on received requests and only bundles the minimal code necessary. Learn more in the [core concepts docs](/TRPG/docs/core-concepts#compiling-by-request).
-
-This strategy makes TRPG extremely fast when first starting up the dev server. We compute only the code necessary to render the page, then ship it to the browser in a single chunk. At large scale, this ends up being significantly faster than Native ESM.
-
-## Summary
-
-We wanted to:
-
-- Build a bundler. Bundlers outperform Native ESM when working on large applications.
-- Use incremental computation. The Turbo engine brings this into the core of TRPG’s architecture - maximizing speed and minimizing work done.
-- Optimize our dev server’s startup time. For that, we build a lazy asset graph to compute only the assets requested.
-
-That’s why we chose to build TRPG.
+...
\ No newline at end of file
diff --git a/docs/pages/TRPG/index.mdx b/docs/pages/TRPG/index.mdx
index 1368e12..044d3b8 100644
--- a/docs/pages/TRPG/index.mdx
+++ b/docs/pages/TRPG/index.mdx
@@ -1,5 +1,5 @@
 ---
-overrideTitle: "TRPG - The successor to webpack"
+overrideTitle: "TRPG 模块，基于HydroRollCore的规则包运行"
 description: "TRPG balabala."
 ---
 
diff --git a/docs/pages/_meta.json b/docs/pages/_meta.json
index aa6748f..f418cde 100644
--- a/docs/pages/_meta.json
+++ b/docs/pages/_meta.json
@@ -10,7 +10,7 @@
       "toc": true
     }
   },
-  "AI": "AI",
+  "MODEL": "MODEL",
   "TRPG": "TRPG",
   "blog": {
     "title": "Blog",
@@ -23,10 +23,6 @@
     "title": "Confirm",
     "display": "hidden"
   },
-  "terms": {
-    "title": "Terms of Service",
-    "display": "hidden"
-  },
   "privacy": {
     "title": "Privacy Policy",
     "display": "hidden"
diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx
index b5b08bd..5090e7f 100644
--- a/docs/pages/index.mdx
+++ b/docs/pages/index.mdx
@@ -1,5 +1,5 @@
 ---
-description: "Turbo is an incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust."
+description: "HydroRoll'水系是一个基于nlp多任务模型的跨平台骰系"
 ---
 
 import LandingPage from "../components/pages/landing";
diff --git a/docs/pages/privacy.mdx b/docs/pages/privacy.mdx
index 273d492..52bf597 100644
--- a/docs/pages/privacy.mdx
+++ b/docs/pages/privacy.mdx
@@ -1,5 +1,5 @@
 ---
-description: See our privacy policy and how it relates to you.
+description: 隐私政策
 hidden: true
 headeronly: true
 container: true
@@ -9,7 +9,7 @@ toc: true
 
 ## Privacy Policy
 
-Copyright (c) 2023 简律纯(HsiangNianian)
+Copyright (c) 2023 HydroRoll-Team
 
 版权所有本软件及其相关文档文件（“软件”），并授予在GPL 3.0许可下使用，复制，修改和分发该软件。
 
@@ -43,4 +43,4 @@ Copyright (c) 2023 简律纯(HsiangNianian)
 
 ## Contact
 
-如果你对这项使用条款有任何问题或建议, 请通过 admin@jyunko.cn 联系我。
\ No newline at end of file
+如果你对这项使用条款有任何问题或建议, 请通过 contact@retrofor.space 联系我们。
\ No newline at end of file
diff --git a/docs/pages/terms.mdx b/docs/pages/terms.mdx
deleted file mode 100644
index 1f890e2..0000000
--- a/docs/pages/terms.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-description: See our terms of our service and how they relate to you.
-hidden: true
-headeronly: true
-container: true
-searchable: false
----
-
-# Turborepo.org Internet Web Site Terms of Service
-
-THE TERMS AND CONDITIONS SET FORTH BELOW (THE "TERMS") GOVERN YOUR USE OF THIS SITE. THESE TERMS ARE A LEGAL CONTRACT BETWEEN YOU AND VERCEL INC. ("Vercel", "WE" OR "US") AND GOVERN YOUR ACCESS TO, AND USE OF, THE TURBOREPO.ORG WEBSITE (THE "SITE"). IF YOU DO NOT AGREE WITH ANY OF THESE TERMS, DO NOT ACCESS OR OTHERWISE USE THIS SITE OR ANY INFORMATION CONTAINED ON THIS SITE. YOUR USE OF THIS SITE SHALL BE DEEMED TO BE YOUR AGREEMENT TO ABIDE BY EACH OF THE TERMS SET FORTH BELOW. VERCEL MAY MAKE CHANGES TO THE CONTENT OFFERED ON THIS SITE AT ANY TIME. VERCEL CAN CHANGE THESE TERMS AT ANY TIME. IF VERCEL MAKES ANY CHANGES, VERCEL WILL POST AN UPDATED TERMS OF USE ON THIS SITE AND MAY SEND REGISTERED USERS AN EMAIL NOTICE OF THE CHANGES. IF ANY MODIFICATION IS UNACCEPTABLE TO YOU, YOU SHALL CEASE USING THIS SITE. IF YOU DO NOT CEASE USING THIS SITE, YOU WILL BE DEEMED TO HAVE ACCEPTED THE CHANGE.
-
-TURBOREPO SOFTWARE IS SEPARATELY MADE AVAILABLE PURSUANT TO AN OPEN SOURCE LICENSE AND YOU MAY FIND LINKS TO THE TURBOREPO SOFTWARE AND ITS ASSOCIATED LICENSES ON THIS SITE.
-
-## General Use Restrictions
-
-Vercel provides various content through this Site. Certain information, documents, documentation, products and services provided on and through this Site, including content, logos, graphics and images (together, the "Materials") are made available to you by Vercel and are the copyrighted and/or trademarked work of Vercel or Vercel's licensors.
-
-Vercel grants you a limited, personal, non-exclusive and non-transferable license to use and to display and to make one copy of the Materials solely for your personal or internal business use. Except for the license set forth in the preceding sentence above, you acknowledge and agree that you have no right to modify, edit, copy, reproduce, create derivative works of, reverse engineer, alter, enhance or in any way exploit any of the Materials in any manner. This limited license terminates automatically, without notice to you, if you breach any of these Terms. Except as stated herein, you acknowledge that you have no right, title or interest in or to this Site, or any Materials.
-
-## Privacy Policy
-
-Your use of this Site is governed by our Privacy Policy, which is available at https://hydroroll.retrofor.space/privacy (the "Privacy Policy").
-
-## Third Party Content
-
-Certain information and other content on the Site may be the material of third party licensors and suppliers to Vercel ("Third Party Content"). The Third Party Content is, in each case, the copyrighted and/or trademarked work of the creator/licensor. You agree to only display the Third Party Content on your computer solely for your personal or internal business use. You acknowledge and agree that you have no right to download, cache, reproduce, modify, display (except as set forth in this paragraph), edit, alter or enhance any of the Third Party Content in any manner unless you have permission from the owner of the Third Party Content. Vercel DISCLAIMS ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES AND CONDITIONS WITH REGARD TO THIRD PARTY CONTENT, INCLUDING, BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
-
-## Links to Other Vercel Sites and Third Party Sites
-
-This Site may be linked to other Vercel sites where you may find other information regarding Vercel and its services.
-This Site also links to other sites that are not Vercel sites. Vercel is providing these links to you only as a convenience, and Vercel is not responsible for such linked sites, including, without limitation, the content or links displayed on such sites.
-
-## Unauthorized Activities
-
-Unauthorized use of any Materials or Third Party Content contained on this Site may violate certain laws and regulations. You agree to indemnify and hold Vercel and its officers, directors, employees, affiliates, agents, licensors, and business partners harmless from and against any and all costs, damages, liabilities, and expenses (including attorneys' fees and costs of defense) Vercel or any other indemnified party suffers in relation to, arising from, or for the purpose of avoiding, any claim or demand from a third party that your use of this Site violates any applicable law or regulation, or the copyrights, trademark rights or other rights of any third party.
-
-## Proprietary Rights
-
-Vercel and Turborepo are trademarks of Vercel. Other trademarks, names and logos on this Site are the property of their respective owners.
-
-Unless otherwise specified in these Terms, all information and screens appearing on this Site, including documents, services, site design, text, graphics, logos, images and icons, as well as the arrangement thereof, are the sole property of Vercel Inc., Copyright © 2021-2022 Vercel Inc. All rights not expressly granted herein are reserved. Except as otherwise required or limited by applicable law, any reproduction, distribution, modification, retransmission, or publication of any copyrighted material is strictly prohibited without the express written consent of the copyright owner or license.
-
-## Disclaimer of Warranties
-
-Your use of this Site is at your own risk. Neither the Materials nor the Third Party Content have been verified or authenticated in whole or in part by Vercel, and they may include inaccuracies or typographical or other errors. Vercel does not warrant the accuracy or timeliness of the Materials or the Third Party Content contained on this Site. Vercel has no liability for any errors or omissions in the Materials and/or the Third Party Content, whether provided by Vercel or our licensors.
-
-VERCEL, FOR ITSELF AND ITS LICENSORS, MAKES NO EXPRESS, IMPLIED OR STATUTORY REPRESENTATIONS, WARRANTIES, OR GUARANTEES IN CONNECTION WITH THIS SITE, ANY MATERIALS, OR THIRD PARTY CONTENT, RELATING TO THE QUALITY, SUITABILITY, TRUTH, ACCURACY OR COMPLETENESS OF ANY INFORMATION OR MATERIAL CONTAINED OR PRESENTED ON THIS SITE AND/OR THE RESULTS OBTAINED FROM THE USE OF THIS SITE, INCLUDING WITHOUT LIMITATION THE MATERIALS AND THE THIRD PARTY CONTENT. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THIS SITE, THE SERVICES, MATERIALS, THIRD PARTY CONTENT, AND ANY INFORMATION OR MATERIAL CONTAINED OR PRESENTED ON THIS SITE IS PROVIDED TO YOU ON AN "AS IS," "AS AVAILABLE" AND "WHERE-IS" BASIS WITH NO WARRANTY OF IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT OF THIRD PARTY RIGHTS. VERCEL DOES NOT PROVIDE ANY WARRANTIES AGAINST VIRUSES, SPYWARE OR MALWARE THAT MAY BE INSTALLED ON YOUR COMPUTER. VERCEL HAS SOLE DISCRETION WHETHER TO ACCEPT OR REJECT YOU AS AN EXPERT OR A CLIENT.
-
-## Limitation of Liability
-
-VERCEL SHALL NOT BE LIABLE TO YOU FOR ANY DAMAGES RESULTING FROM YOUR DISPLAYING, COPYING, OR DOWNLOADING ANY MATERIAL OR THIRD PARTY CONTENT TO OR FROM THIS SITE. IN NO EVENT SHALL VERCEL BE LIABLE TO YOU FOR ANY INDIRECT, EXTRAORDINARY, EXEMPLARY, PUNITIVE, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF DATA, REVENUE, PROFITS, USE OR OTHER ECONOMIC ADVANTAGE) HOWEVER ARISING, EVEN IF VERCEL KNOWS THERE IS A POSSIBILITY OF SUCH DAMAGE OR FOR DAMAGES IN THE AGGREGATE EXCEEDING THE AMOUNT OF ONE HUNDRED DOLLARS.
-
-## Local Laws; Export Control
-
-Vercel controls and operates this Site from its headquarters in the United States of America and the Materials and/or Third Party Content may not be appropriate or available for use in other locations. If you use this Site outside the United States of America, you are responsible for following applicable local laws.
-
-## General
-
-If you violate these Terms, Vercel may terminate and/or suspend your access to this Site without notice. The proprietary rights, disclaimer of warranties, representations made by you, indemnities, limitations of liability and general provisions shall survive any termination of these Terms.
-
-Vercel may change these Terms from time to time by providing thirty (30) days prior notice either by posting a notice at the Site. You can review the most current version of these Terms at any time at this Site. The revised Terms will become effective thirty (30) days after Vercel posts or sends you notice of such changes, and if you use the Site after that date, your use will constitute acceptance of the revised Terms. If any change to these Terms are not acceptable to you, your only remedy is to stop using the Site. If any provision of these Terms are found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that these Terms will otherwise remain in full force and effect and enforceable. You may not assign, transfer or sublicense without the prior written consent of Vercel, but Vercel may assign or transfer these Terms, in whole or in part, without restriction. Any attempted assignment or transfer of these Terms by the parties in contravention of the foregoing shall be null and void. These Terms are the complete and exclusive statement of the mutual understanding of the parties and supersedes and cancels all previous written and oral agreements, communications and other understandings relating to the subject matter of these Terms, and that all amendments must be in writing signed by both parties, except as otherwise provided herein. Vercel's failure to exercise or enforce any right or provision of these Terms shall not be a waiver of that right. No agency, partnership, joint venture, or employment is created as a result of these Terms and neither party has any authority of any kind to bind the other party in any respect whatsoever. In any action or proceeding to enforce rights under these Terms, the prevailing party will be entitled to recover costs and attorneys' fees. Except as stated above, all notices under these Terms will be in writing and will be deemed to have been duly given when received, if personally delivered; when receipt is electronically confirmed, if transmitted by email; the day after it is sent, if sent for next day delivery by recognized overnight delivery service; and upon receipt, if sent by certified or registered mail, return receipt requested.
-
-Any delays in or failure of performance of Vercel shall not constitute a default hereunder or give rise to any claims for damages if, to the extent that, and for such period that, such delays or failures of performance are caused by any events beyond the reasonable control of Vercel including, without limitation, any of the following specific occurrences: acts of God or the public enemy, acts of terrorism, pandemics, epidemics, labor strikes, expropriation or confiscation of facilities, compliance with any unanticipated duly promulgated governmental order, acts of war, rebellion or sabotage or damage resulting therefrom, fires, floods, explosion, or riots.
-
-## Governing Law; Disputes; Arbitration.
-
-**Law.** These Terms shall be governed by the laws of the State of California without regard to its conflict of laws provisions and the parties agree to the exclusive jurisdiction of the state and federal courts in San Francisco county.
-
-**Binding Contract.** You acknowledge that these Terms are a contract between you and Vercel, even though it is electronic and is not physically signed by you and Vercel, and it governs your use of the Site.
-
-**Arbitration.** Certain portions of this Section are deemed to be a "written agreement to arbitrate" pursuant to the Federal Arbitration Act ("FAA"). You and Vercel expressly agree and intend that this Section satisfies the "writing" requirement of the Federal Arbitration Act. This Section can only be amended by mutual agreement. For purposes of this Section, "Claims" means collectively, and without limitation, any and all claims, injuries, demands, liabilities, disputes, causes of action (including statutory, contract, negligence, or other tort theories), proceedings, obligations, debts, liens, fines, charges, penalties, contracts, promises, costs, expenses (including attorneys' fees, whether incurred pre-litigation, pre-trial, at trial, on appeal, or otherwise), damages of any kind whatsoever (including consequential, compensatory, or punitive damages), or losses (whether known, unknown, asserted, non-asserted, fixed, conditional, or contingent) that arise from or relate to (i) the Site, including any and all contents, materials and software related thereto, and/or (ii) your use of the Site.
-
-**Informal Dispute Resolution.** If any Claim arises out of or relates to the Site or these Terms, other than as may be provided herein, then you and Vercel agree to send notice to the other providing a reasonable description of the Claim, along with a proposed resolution of it. Vercel notice to you will be sent based on the most recent contact information that you provided Vercel. If no such information exists or if such information is not current, Vercel has no obligation under this Section. For a period of sixty (60) days from the date of receipt of notice from the other party, you and Vercel will engage in a dialog to attempt to resolve the Claim, though nothing will require either you or Vercel to resolve the Claim on terms with respect to which you and Vercel, in each of the parties' sole discretion, is not comfortable.
-
-**Applicable Law.** If you and Vercel cannot resolve a Claim, within sixty (60) days of the receipt of the notice, then you agrees that that any such Claim and all other disputes arising out of or relating to the interpretation, applicability, enforceability or formation of these Terms, including, but not limited to any claim that all or any part of these Terms are void or voidable, or whether a claim is subject to arbitration relating to your use of the Site, will be resolved by binding arbitration, rather than in court. The FAA, not state law, shall govern the arbitrability of such disputes, including the class action waiver below. However, you and Vercel agree that California state law or United States federal law shall apply to, and govern, as appropriate, any and all Claims or disputes arising between you and Vercel regarding these Terms and the Site, whether arising or stated in contract, statute, common law, or any other legal theory, without regard to choice of law principles. There is no judge or jury in arbitration, and court review of an arbitration award is limited. However, an arbitrator must follow the terms of these Terms as a court would. THIS SECTION, INCLUDING THE PROVISIONS ON BINDING ARBITRATION AND CLASS ACTION WAIVER, SHALL SURVIVE ANY TERMINATION OF YOUR ACCOUNT OR THE SERVICE.
-
-**Arbitration Request.** To begin an arbitration proceeding, you must send a letter requesting arbitration and describing your claim to Vercel at 340 S Lemon Ave #4133, Walnut CA, 91789. The arbitration will be conducted by JAMS in accordance with the JAMS Streamlined Arbitration Procedure Rules in effect at the time the arbitration is initiated, excluding any rules or procedures governing or permitting class actions. Payment of all filing, administration and arbitrator fees will be governed by JAMS's rules. The arbitration shall take place in San Francisco, California or at such other venue (and pursuant to such procedures) as is mutually agreed upon. You can obtain JAMS procedures, rules, and fee information as follows: JAMS: 800.352.5267 and https://www.jamsadr.com.
-
-**Fees.** You and Vercel will pay the administrative and arbitrator's fees and other costs in accordance with the applicable arbitration rules; but if applicable arbitration rules or laws require Vercel to pay a greater portion or all of such fees and costs in order for this Section to be enforceable, then Vercel will have the right to elect to pay the fees and costs and proceed to arbitration. Arbitration rules may permit Vercel to recover attorneys' fees. Vercel will not seek to recover attorneys' fees and costs in arbitration unless the arbitrator determines the claims are frivolous.
-
-**Class Action Waiver.** YOU AND VERCEL EACH AGREE THAT ANY DISPUTE RESOLUTION PROCEEDING WILL BE CONDUCTED ONLY ON AN INDIVIDUAL BASIS AND NOT IN A CLASS, CONSOLIDATED OR REPRESENTATIVE ACTION. You and Vercel each agree that such proceeding shall take solely by means of judicial reference pursuant to California Code of Civil Procedure section 638.
-
-**Exceptions.** Notwithstanding the agreement to resolve all disputes through arbitration, you or Vercel may bring suit in court to enjoin infringement or other misuse of intellectual property rights (including patents, copyrights, trademarks, trade secrets, and moral rights, but not including privacy rights). You or Vercel may also seek relief in small claims court for Claims within the scope of that court's jurisdiction. In the event that the arbitration provisions above are found not to apply to you or to a particular Claim, either as a result of your decision to opt-out of the arbitration provisions or as a result of a decision by the arbitrator or a court order, you agree that the venue for any such Claim or dispute is exclusively that of a state or federal court located in San Francisco County, California. You and Vercel agree to submit to the personal jurisdiction of the courts located within San Francisco County, California for the purpose of litigating all such Claims or any other disputes arising out of or relating to the interpretation, applicability, enforceability or formation of these Terms or your use of the Site in the event that the arbitration provisions are found not to apply. In such a case, should Vercel prevail in litigation against you to enforce its rights under these Terms, Vercel shall be entitled to its costs, expenses, and reasonable attorneys' fees (whether incurred at or in preparation for trial, appeal or otherwise) incurred in resolving or settling the dispute, in addition to all other damages or awards to which Vercel may be entitled.
-
-**Restrictions.** TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, IF YOU OR VERCEL WANT TO ASSERT A DISPUTE AGAINST THE OTHER, THEN YOU OR VERCEL MUST COMMENCE IT (BY DELIVERY OF WRITTEN NOTICE AS SET FORTH HEREIN) WITHIN ONE (1) YEAR AFTER THE DISPUTE ARISES OR IT WILL BE FOREVER BARRED. "Commencing" means, as applicable: (i) by delivery of written notice as set forth herein; (ii) filing for arbitration with JAMS as set forth herein; or (iii) filing an action in state or federal court. This provision will not apply to any legal action taken by Vercel to seek an injunction or other equitable relief in connection with any losses (or potential losses) relating to the Site, intellectual property rights of Vercel, and/or Vercel's provision of the Site.
-
-**Opt-Out.** You have the right to opt-out and not be bound by the arbitration and class action waiver provisions set forth above by sending written notice of your decision to opt-out to: privacy@vercel.com with the subject line "COMPANY ARBITRATION AND CLASS ACTION WAIVER OPT-OUT". The notice must be sent within thirty (30) days of your first use of the Site, otherwise you shall be bound to arbitrate any disputes in accordance with these Terms providing for binding arbitration. If you opt-out of these arbitration provisions, Vercel also will not be bound by them.
-
-Date last updated: December 8th, 2021