|
1 | 1 | --- |
2 | 2 | title: Overview |
3 | | -description: Here's where your user finds out if your project is for them. |
| 3 | +description: Learn about DataMate, an enterprise-grade data processing system designed to empower AI applications and streamline data workflows. |
4 | 4 | weight: 1 |
5 | 5 | --- |
6 | 6 |
|
7 | 7 | {{% pageinfo %}} |
8 | 8 |
|
9 | | -This is a placeholder page that shows you how to use this template site. |
| 9 | +DataMate simplifies end-to-end data management for AI-driven enterprises, combining multi-modal support, high performance, and one-stop services to accelerate your data workflows. |
10 | 10 |
|
11 | 11 | {{% /pageinfo %}} |
12 | 12 |
|
13 | | -The Overview is where your users find out about your project. Depending on the |
14 | | -size of your docset, you can have a separate overview page (like this one) or |
15 | | -put your overview contents in the Documentation landing page (like in the Docsy |
16 | | -User Guide). |
| 13 | +# Overview |
| 14 | +description: Learn about DataMate, an enterprise-grade data processing system designed to empower AI applications and streamline data workflows. |
| 15 | +weight: 1 |
17 | 16 |
|
18 | | -Try answering these questions for your user in this page: |
| 17 | +{{% pageinfo %}} |
| 18 | +DataMate simplifies end-to-end data management for AI-driven enterprises, combining multi-modal support, high performance, and one-stop services to accelerate AI落地. |
| 19 | +{{% /pageinfo %}} |
19 | 20 |
|
20 | 21 | ## What is it? |
21 | | - |
22 | | -Introduce your project, including what it does or lets you do, why you would use |
23 | | -it, and its primary goal (and how it achieves it). This should be similar to |
24 | | -your README description, though you can go into a little more detail here if you |
25 | | -want. |
| 22 | +DataMate is an enterprise-grade data processing system tailored for model training, AI applications, and data flywheel scenarios. It integrates multi-modal data management, high-performance data processing, and rich data service capabilities to provide industry customers with one-stop data handling—covering processing, refinement, and management. Its core goal is to boost data processing efficiency, reduce related costs, and facilitate the smooth implementation of enterprise AI applications. |
26 | 23 |
|
27 | 24 | ## Why do I want it? |
28 | | - |
29 | | -Help your user know if your project will help them. Useful information can |
30 | | -include: |
31 | | - |
32 | | -- **What is it good for?**: What types of problems does your project solve? What |
33 | | - are the benefits of using it? |
34 | | - |
35 | | -- **What is it not good for?**: For example, point out situations that might |
36 | | - intuitively seem suited for your project, but aren't for some reason. Also |
37 | | - mention known limitations, scaling issues, or anything else that might let |
38 | | - your users know if the project is not for them. |
39 | | - |
40 | | -- **What is it _not yet_ good for?**: Highlight any useful features that are |
41 | | - coming soon. |
42 | | - |
43 | | -## Where should I go next? |
44 | | - |
45 | | -Give your users next steps from the Overview. For example: |
46 | | - |
47 | | -- [Getting Started](/docs/getting-started/): Get started with $project |
48 | | -- [Examples](/docs/examples/): Check out some example code! |
| 25 | +### What is it good for? |
| 26 | +- Solves complex data management challenges in AI workflows, including handling multi-modal data (e.g., text, image, audio) uniformly. |
| 27 | +- Enhances data processing speed with high-performance computing capabilities, shortening the cycle of model training and AI application development. |
| 28 | +- Reduces operational costs by replacing fragmented data tools with a unified platform, eliminating the need for multiple system integrations. |
| 29 | +- Supports end-to-end data operations, from collection to processing, management, and service provision, aligning with the closed-loop needs of data flywheels. |
| 30 | + |
| 31 | +### What is it not good for? |
| 32 | +- Does not provide custom hardware integration services; it focuses on software-layer data processing and management. |
| 33 | +- Not optimized for real-time transactional data processing (e.g., high-frequency financial transactions) where ultra-low latency is the primary requirement. |
0 commit comments