Born for AI, Next-Gen Enterprise-Level AI Application Development Platform
๐ Online Documentation | ๐ Quick Start | ๐ค Contributing | ๐ฌ Community
Language Versions / ่ฏญ่จ็ๆฌ: ๐บ๐ธ English | ๐จ๐ณ ไธญๆ | ๐ค Contributing Guide | ๐ค ่ดก็ฎๆๅ
JitAi Developer Documentation is a comprehensive technical documentation collection for JitAi platform users and developers. This project is committed to providing clear, accurate, and easy-to-understand technical documentation to help developers quickly get started and master the various features of the JitAi platform.
- ๐ Comprehensive Coverage: Complete development guide from quick start to advanced topics
- ๐ Quick Start: Develop your first AI application in 5 minutes
- ๐ฏ Practice-Oriented: Rich practical tutorials and best practices
- ๐ง Developer-Friendly: Detailed API documentation and development toolchain instructions
- ๐ Multi-Platform Support: Support for desktop (Windows/Mac) and server (Docker) versions
- ๐ฑ Responsive Design: Perfect adaptation to various devices and screen sizes
- Quick Start: Platform installation, environment configuration, first AI application development
- System Overview: Architecture design, application specifications, element specifications, runtime mechanisms
- Development Guide: BaseApp, JitAi components, platform API detailed instructions
- Practical Tutorials: Complete project development cases such as CRM applications
- Advanced Guide: Local development and debugging, frontend code debugging, server log viewing
- API Reference: Complete reference documentation for frontend API and backend API
- Node.js: >= 18.0.0
- Yarn: >= 1.22.0 (recommended) or npm >= 8.0.0
-
Clone the Repository
git clone https://github.com/jitai-team/jitai-docs.git cd jitai-docs -
Install Dependencies
yarn install # or use npm npm install -
Start Development Server
yarn start # or use npm npm run start -
Access Documentation
Open your browser and visit http://localhost:3000
# Build static files
yarn build
# Preview build results
yarn servejitai-docs/
โโโ docs/ # Documentation content
โ โโโ tutorial/ # Tutorial documentation
โ โ โโโ 00ๅฟซ้ไธๆ/ # Quick start guide
โ โ โโโ 01ๆฆ่ฟฐ/ # System overview
โ โ โโโ 02ๅฎไพๆ็จ/ # Practical cases
โ โ โโโ 03ๆๅ/ # Development guide
โ โ โโโ 04่ฟ้ถๆๅ/ # Advanced content
โ โโโ cases/ # Case studies
โ โโโ community/ # Community related
โโโ blog/ # Blog posts
โโโ src/ # Source code
โ โโโ components/ # React components
โ โโโ css/ # Style files
โ โโโ pages/ # Page components
โโโ static/ # Static assets
โโโ docusaurus.config.ts # Configuration file
โโโ sidebars.ts # Sidebar configuration
We warmly welcome and appreciate contributions from every developer! Whether you've found documentation errors, want to improve content quality, or hope to add new features, your participation will make this project better.
If you find errors, inaccurate descriptions, or other issues in the documentation:
- Check the Issues page to confirm the issue hasn't been reported yet
- Create a new Issue with detailed description:
- Specific location of the issue (page link, section title, etc.)
- Detailed description of the issue
- Suggested fix (if any)
- Related screenshots or error messages
- Fork this repository to your GitHub account
- Create a feature branch:
git checkout -b feature/improve-docs - Make changes:
- Fix documentation errors or improve content expression
- Add new tutorials or examples
- Improve API documentation
- Optimize documentation structure and navigation
- Local testing: Ensure modified documentation builds and displays correctly
- Commit changes:
git commit -am 'docs: improve quick start guide' - Push branch:
git push origin feature/improve-docs - Create Pull Request with detailed description of your changes
- Tech Stack: Project built with Docusaurus + React + TypeScript
- Code Standards: Follow existing code style and naming conventions
- Testing: Ensure all changes are thoroughly tested
- Documentation: Add corresponding usage instructions for new features
- Docusaurus Features: Make full use of Docusaurus components and plugin system
-
Commit Message Format:
<type>: <description> Types include: - docs: Documentation updates - feat: New features - fix: Bug fixes - style: Code formatting adjustments - refactor: Code refactoring -
Branch Naming Convention:
feature/feature-description- New feature developmentfix/issue-description- Bug fixesdocs/documentation-description- Documentation updates
Thanks to all developers who have contributed to this project:
Join our developer community to exchange experiences and get help:
- GitHub Discussions: Project Discussion Area
- GitHub Issues: Issue Reports and Feature Requests
- Official Website: https://jit.pro
- Thanks to all developers who contributed code and documentation to this project
- Thanks to community members for valuable feedback and suggestions
If this project is helpful to you, please give us a โญ
Made with โค๏ธ by Wuhan Wanyun Technology Team