## 1. Project Overview & Quickstart (mylxsw/aidea) ## File: README.md # AIdea - AI Chat, Collaboration & Image Generation English | [中文](./README.zh-CN.md) [](https://app.fossa.com/projects/custom%2B39727%2Fgithub.com%2Fmylxsw%2Faidea?ref=badge_shield) [](https://trendshift.io/repositories/1013) An APP that integrates mainstream large language models and image generation models, built with Flutter, with fully open-source code. Download & Try: https://aidea.aicode.cc Open Source Repositories: - Client: https://github.com/mylxsw/aidea - Server: https://github.com/mylxsw/aidea-server - Docker Deployment: https://github.com/mylxsw/aidea-docker ## Development & Build Environment The default branch `main` is the v2 version, currently under active development. If you need to self-host, please switch to the [v1.x](https://github.com/mylxsw/aidea/tree/v1.x) branch. ```bash git checkout v1.x ``` To set up a development environment for compiling and packaging the APP, you can refer to the following articles (more articles will be added over time): - [AIdea Development Environment Tutorial (1): Flutter Frontend Setup](https://mp.weixin.qq.com/s/bgAIH6s7t5IREusK_WtpRg) - [AIdea Development Environment Tutorial (2): Golang Server Setup](https://mp.weixin.qq.com/s?__biz=MzA3NTU1NDk4Mg==&mid=2454663711&idx=1&sn=c2c66abc20f8e0900afe645ff1f552ac&chksm=88d55bd6bfa2d2c063ea15a4e8864c197009b49233c710b85725f1aa946836e15a26439c69a7&scene=178&cur_album_id=3204997940193296389#rd) - [AIdea Development Environment Tutorial (3): Windows Build Environment Setup](https://mp.weixin.qq.com/s?__biz=MzA3NTU1NDk4Mg==&mid=2454663731&idx=1&sn=2aa4841daeb8dc4132e8abe63f585996&chksm=88d55bfabfa2d2ecce8224dcf23da6f911d3d8324121d141fd5c0324197c6f4845dd63639ac2&scene=178&cur_album_id=3204997940193296389#rd) - [Flutter App Windows Installer Creation Tutorial](https://mp.weixin.qq.com/s?__biz=MzA3NTU1NDk4Mg==&mid=2454663689&idx=1&sn=73c93edd9ddacb2d4c36061cc79be059&chksm=88d55bc0bfa2d2d6ecaa7979835431467105d9572953f1e96c0f735df3fe60d4f6d6137f041d&scene=178&cur_album_id=3204997940193296389#rd) > Some users encounter build failures, which can be very frustrating. This is not a bug -- it is a known characteristic of Flutter. Build failures are common as the Flutter version changes. > To be safe, you can refer to my local environment configuration: > > ## Self-Hosting / Private Deployment If you do not want to use the managed cloud service, you can deploy the server yourself. [See deployment instructions here](https://github.com/mylxsw/aidea-server/blob/main/docs/deploy.md). If you prefer not to set it up yourself, you can contact me for assisted deployment. See [VIP Deployment Service](https://github.com/mylxsw/aidea-server/blob/main/docs/deploy-vip.md) for details. ## Community & Support - WeChat Tech Group: Add WeChat ID `x-prometheus` as a friend for an invitation to the group. - WeChat Official Account: ## Screenshots Mobile MacOS Windows ## License MIT Copyright (c) 2025, mylxsw --- ## File: ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md # Launch Screen Assets You can customize the launch screen with your own desired assets by replacing the image files in this directory. You can also do it by opening your Flutter project's Xcode project with `open ios/Runner.xcworkspace`, selecting `Runner/Assets.xcassets` in the Project Navigator and dropping in the desired images. ## 2. Official Technical Reference & Guides (mylxsw/mylxsw.github.io) # Gulu AI website The company homepage for [gulu.ai](https://gulu.ai), built with React, TypeScript and Vite. ## Develop ```bash npm install npm run dev # http://localhost:5173 npm run build # type-check, build to docs/, and preserve the custom domain npm run preview # serve the production build npm run lint ``` `docs/` is the production static site. GitHub Pages publishes the `main` branch at `/docs` on `https://gulu.ai/`. The build preserves the root `CNAME` (or an explicit `PAGES_CNAME`, `CNAME`, or `VITE_CNAME` environment override) and copies `public/.nojekyll` to disable Jekyll processing. ## Editing content - **Products:** `src/data/products.ts`. The first product with `featured: true` is the large card. To use a real logo, put the image in `public/logos/` and set `logo: '/logos/.png'`. Without a logo, the card shows the two-letter `monogram`. - **Navigation, model list, contact email:** `src/data/site.ts`. The contact email preserves the address from the previous live homepage. - **Colors and fonts:** the tokens at the top of `src/styles/global.css`. - **Company logo:** `public/brand/gulu-mark.svg` is the vector version of the approved violet G concept. Navigation, footer, and browser icon use the same file. The adjacent wordmark inherits the foreground color for dark/light backgrounds. The five product icons in `public/logos/` are restored unchanged from `backup/pre-gulu-ai-2026-10-08:src/assets/`. They were checked against the corresponding product projects, including the current AIdea iOS app icon. These bundled images replace the letter placeholders and do not depend on external image hosts. ## Structure ``` src/ App.tsx page sections in order data/ products and site content components/ one component (and its CSS) per section styles/global.css design tokens and shared styles ``` ## Publish and rollback Use `npm ci`, `npm run lint`, and `npm run build` before committing the source and generated `docs/` files to `main`. The existing `make run`, `make build`, and `make push` commands remain available. GitHub Pages keeps its existing custom domain and publishing source; no DNS or hosting changes are required. The homepage was imported from [`mylxsw/gulu-ai-website`](https://github.com/mylxsw/gulu-ai-website) at commit `442a81232bacf738f0aade462b908a95a7ea4c1f`. Deployment-only adaptations are the `docs/` output, relative asset base, CNAME build step, `.nojekyll`, the previous contact email, and excluding generated `docs/` assets from lint. The complete previous source and deployed assets are preserved in [`backup/pre-gulu-ai-2026-10-08`](https://github.com/mylxsw/mylxsw.github.io/tree/backup/pre-gulu-ai-2026-10-08) at commit `294b0f89fecbd256f79fe11a310bc5e636b8d509`. To restore the previous site, revert the migration commit on `main`, push, and verify the resulting GitHub Pages deployment. Do not force-push or change the Pages source to perform a rollback.