添加simulator部分

docs/.vitepress/config.mts

@@ -75,7 +75,7 @@ function sidebarDocument(): DefaultTheme.SidebarItem[] {
   return [
     {
       text: 'Devstar是什么',
-      link: '/document/index',
+      link: '/devstar/index',
       items: []
     } as any,
     {
@@ -86,7 +86,7 @@ function sidebarDocument(): DefaultTheme.SidebarItem[] {
         { text: '对比Gitea与其它Git托管工具', link: 'https://docs.gitea.com/zh-cn/installation/comparison' },
         { text: '数据库准备', link: 'https://docs.gitea.com/zh-cn/installation/database-prep' },
         // { text: '数据库准备', link: '/document/installation/from-source' },
-        { text: '使用shell脚本安装', link: '/document/installation/install-via-shell-script' },
+        { text: '使用shell脚本安装', link: '/devstar/installation/install-via-shell-script' },
         { text: '使用二进制文件安装', link: 'https://docs.gitea.com/zh-cn/installation/install-from-binary' },
         { text: '包管理器安装', link: 'https://docs.gitea.com/zh-cn/installation/install-from-package' },
         { text: '使用源代码安装', link: 'https://docs.gitea.com/zh-cn/installation/install-from-source' },
@@ -130,7 +130,7 @@ function sidebarDocument(): DefaultTheme.SidebarItem[] {
       collapsible: true, // 使整个组可折叠
       collapsed: true, // 默认展开
       items: [
-        { text: '结合AI快速开始', link: 'document/usage/quick-start-with-ai' },
+        { text: '结合AI快速开始', link: 'devstar/usage/quick-start-with-ai' },
         {
           text: 'Actions',
           collapsible: true, // 使整个组可折叠

docs/.vitepress/theme/style.css

@@ -13,6 +13,16 @@
   background-color: white !important;
 }
 
+/* 去除掉每个h2标题上面的线 */
+.vp-doc h2 {
+  border-top: none;
+}
+
+/* 去除掉页面底部导航的横线 */
+nav.prev-next {
+  border-top: none !important;
+}
+
 /* 首页图片 */
 img.VPImage.image-src {
   max-width: 500px !important;

docs/cloudbuild/index.md

@@ -1,5 +1,5 @@
 # 分布式编译系统CloudBuild
-
+![alt text](/public/cloudbuild/promotional-graphic-cloudbuild.jpg)
 ##  为什么需要分布式编译技术
 - 大型项目过长的编译耗时将会给开发、测试和调试都带来延迟，所以缩短大型项目的编译时间的分布式编译系统有重要意义
 - 使用分布式编译系统编译项目可以利用计算机集群提高编译效率，缩短项目编译时间
@@ -25,3 +25,55 @@ CloudBuild主程序分为三个部分：Client、Server、Executor。
 
 ### 系统分层结构
 ![alt text](/public/cloudbuild/layered-system-architecture.png)
+
+## 运行原理与流程
+
+### 分布式编译原理
+![alt text](/public/cloudbuild/compiler-principles.png)
+
+### CloudBuild客户端
+CloudBuild客户端基于Ninja改造，有下面这些优势
+- 兼容使用Ninja编译的项目
+- 使用远程执行的方式提高编译时并发度
+- 使用编译缓存减少需要编译的任务数量
+
+### CloudBuild服务端
+- 使用远程执行的方法提高编译时并发度，实现了任务分发至远程节点同步执行
+- 使用分布式任务调度提高任务调度效率和计算节点资源利用率，避免集中式调度的任务阻塞问题
+- 使用编译缓存结合内容寻址存储技术减少网络传输量、避免重复上传与重复编译
+
+### CloudBuild优势
+- 低成本：组成executor的机器不需要使用专门的高性能计算型机器，可使用多个平价的空闲机器
+- 高效：CloudBuild实现分布式编译的功能，相比单机大大提升并发度
+- 兼容Ninja：CloudBuild客户端基于Ninja改造，对于使用Ninja构建和可以转换为Ninja构建的项目不用额外修改构建清单
+
+### CloudBuild执行流程
+- 客户端: 生成远程任务->生成任务依赖->发送任务与依赖
+- 服务端：检查任务缓存->检查依赖完整性->调度任务
+- 编译结点：还原文件目录->还原文件目录->返回编译结果
+
+## AOSP和LLVM上的应用
+### LLVM上的应用效果
+![alt text](/public/cloudbuild/table1.png)
+### AOSP上的应用效果
+![alt text](/public/cloudbuild/table2.png)
+### CloudBuild硬件资源利用率
+4核CPU利用率:
+![alt text](/public/cloudbuild/CPU-utilization-4.png)
+8核CPU利用率:
+![alt text](/public/cloudbuild/CPU-utilization-8.png)
+16核CPU利用率:
+![alt text](/public/cloudbuild/CPU-utilization-16.png)
+
+## CloudBuild使用方法
+### CloudBuild安装
+![alt text](/public/cloudbuild/cloudbuild-installation.png)
+CloudBuild项目地址：https://gitee.com/cloudbuild888/cloudbuild.git
+### CloudBuild分布式编译
+![alt text](/public/cloudbuild/cloudbuild-distributed-compilation.png)
+LLVM项目地址：https://gitee.com/mirrors/LLVM.git
+
+
+
+
+

docs/components/index.vue

@@ -2,7 +2,6 @@
   <section class="tencent-showcase">
     <div class="ten_main">
       <div class="ten_links">
-        <!-- 公司简介卡片 -->
         <a 
           href="/devstar" 
           class="ten_img"
@@ -11,7 +10,7 @@
         >
           <img 
             src="/public/promotional-graphic-devstar.png" 
-            alt="公司简介" 
+            alt="devstar" 
             class="tencent-image"
             :class="{ 'image-hover': hoverItem === 'about' }"
           >
@@ -20,7 +19,6 @@
           </div>
         </a>
 
-        <!-- 企业文化卡片 -->
         <a 
           href="/cloudbuild" 
           class="ten_img"
@@ -29,7 +27,7 @@
         >
           <img 
             src="/public/promotional-graphic-cloudbuild.jpg" 
-            alt="企业文化" 
+            alt="cloudbuild" 
             class="tencent-image"
             :class="{ 'image-hover': hoverItem === 'culture' }"
           >
@@ -38,7 +36,6 @@
           </div>
         </a>
 
-        <!-- 办公地点卡片 -->
         <a 
           href="/simulator" 
           class="ten_img"
@@ -47,7 +44,7 @@
         >
           <img 
             src="/public/promotional-graphic-simulator.jpg" 
-            alt="办公地点" 
+            alt="simulator" 
             class="tencent-image"
             :class="{ 'image-hover': hoverItem === 'office' }"
           >
@@ -62,7 +59,7 @@
 
 <script>
 export default {
-  name: 'TencentShowcase',
+  name: 'Showcase',
   data() {
     return {
       hoverItem: null
@@ -104,11 +101,11 @@ export default {
   transform: translateY(-5px);
 }
 
-/* 图片样式 - 严格按第一张图要求 */
+/* 图片样式  */
 .tencent-image {
   width: 100%;
   height: 200px;
-  object-fit: contain;
+  /* object-fit: contain; */
   object-position: center;
   background-color: #f5f7fa;
   /* padding: 20px; */
@@ -121,7 +118,7 @@ export default {
   background-color: #e3f2fd;
 }
 
-/* 文字区域 - 按第三张图效果 */
+/* 文字区域  */
 .ten_img_txt {
   position: absolute;
   bottom: 0;
@@ -148,7 +145,7 @@ export default {
   padding-bottom: 8px;
 }
 
-/* 悬浮时显示的下划线 - 按第三张图要求 */
+/* 悬浮时显示的下划线  */
 .text-hover h2::after {
   content: "";
   position: absolute;

docs/devstar/usage/quick-start-with-ai.md

@@ -1,7 +1,5 @@
 # 结合AI快速开始
 
-## 快速开始
-
 - 确定需求，Al生成代码，Chat with the Al in VSCode/Cursor/Trae/Qode/ Claude Code etc.
 - 初步验证结果，人工检查和测试代码，Code Review/Test Code
 - 将代码提交到Git仓库，发起Pull Request合并代码请求，Chat with DevStar MCP Server

docs/runner/index.md

@@ -1,104 +0,0 @@
----
-sidebar_position: 1
-slug: /
----
-
-# What is Gitea Runner
-
-Act runner is a runner for Gitea based on [Gitea fork](https://gitea.com/gitea/act) of [act](https://github.com/nektos/act). This documentation is a copy of https://gitea.com/gitea/act_runner/src/branch/main/README.md . And it should be updated once that README changed.
-
-## Installation
-
-### Prerequisites
-
-Docker Engine Community version is required for docker mode. To install Docker CE, follow the official [install instructions](https://docs.docker.com/engine/install/).
-
-### Download pre-built binary
-
-Visit [here](https://dl.gitea.com/act_runner/) and download the right version for your platform.
-
-### Build from source
-
-```bash
-make build
-```
-
-### Build a docker image
-
-```bash
-make docker
-```
-
-### Register
-
-```bash
-./act_runner register
-```
-
-And you will be asked to input:
-
-1. Gitea instance URL, like `http://192.168.8.8:3000/`. You should use your gitea instance ROOT_URL as the instance argument
- and you should not use `localhost` or `127.0.0.1` as instance IP;
-2. Runner token, you can get it from `http://192.168.8.8:3000/-/admin/actions/runners`;
-3. Runner name, you can just leave it blank;
-4. Runner labels, you can just leave it blank.
-
-The process looks like:
-
-```text
-INFO Registering runner, arch=amd64, os=darwin, version=0.1.5.
-WARN Runner in user-mode.
-INFO Enter the Gitea instance URL (for example, https://gitea.com/):
-http://192.168.8.8:3000/
-INFO Enter the runner token:
-fe884e8027dc292970d4e0303fe82b14xxxxxxxx
-INFO Enter the runner name (if set empty, use hostname: Test.local):
-
-INFO Enter the runner labels, leave blank to use the default labels (comma-separated, for example, ubuntu-latest:docker://gitea/runner-images:ubuntu-latest):
-
-INFO Registering runner, name=Test.local, instance=http://192.168.8.8:3000/, labels=[ubuntu-latest:docker://gitea/runner-images:ubuntu-latest ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04 ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04].
-DEBU Successfully pinged the Gitea instance server
-INFO Runner registered successfully.
-```
-
-You can also register with command line arguments.
-
-```bash
-./act_runner register --instance http://192.168.8.8:3000 --token <my_runner_token> --no-interactive
-```
-
-If the registry succeed, it will run immediately. Next time, you could run the runner directly.
-
-### Run
-
-```bash
-./act_runner daemon
-```
-
-### Run with docker
-
-```bash
-docker run -e GITEA_INSTANCE_URL=https://your_gitea.com -e GITEA_RUNNER_REGISTRATION_TOKEN=<your_token> -v /var/run/docker.sock:/var/run/docker.sock --name my_runner gitea/act_runner:nightly
-```
-
-### Configuration
-
-You can also configure the runner with a configuration file.
-The configuration file is a YAML file, you can generate a sample configuration file with `./act_runner generate-config`.
-
-```bash
-./act_runner generate-config > config.yaml
-```
-
-You can specify the configuration file path with `-c`/`--config` argument.
-
-```bash
-./act_runner -c config.yaml register # register with config file
-./act_runner -c config.yaml daemon # run with config file
-```
-
-You can read the latest version of the configuration file online at [config.example.yaml](internal/pkg/config/config.example.yaml).
-
-### Example Deployments
-
-Check out the [examples](https://gitea.com/gitea/act_runner/src/branch/main/examples) directory for sample deployment types.

docs/simulator/index.md

@@ -0,0 +1,13 @@
+# simulator
+![alt text](image.png)
+
+## 从vECU到整车仿真
+![alt text](image-1.png)
+![alt text](image-2.png)
+
+## 整车系统级软硬件联合仿真
+![alt text](image-3.png)
+应用场景
+- 算法及软件的快速测试验证：用台架RT-ECU作为开发控制器的快速样件
+- 控制器的常规HIL测试
+- 整车级多控制器的交互测试