docs: reorder README sections, simplify Live Demo badge, add JP screenshots
- Move "How it works" above "Team & Vision" so the technical deep-dive follows the screenshots while reader interest is highest - Simplify the Live Demo badge to a single segment (drop the domain; the badge still links to infiplot.com) - Add the missing Screenshots section to the Japanese README (i18n gap: it was added to zh/en but never backported to ja) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
yuanzonghao
committed by
Zonghao Yuan
Zonghao Yuan
parent
d263437756
commit
6038216751
+23
-23
@@ -9,7 +9,7 @@
|
||||
[](https://github.com/zonghaoyuan/infiplot/network)
|
||||
[](https://github.com/zonghaoyuan/infiplot/issues)
|
||||
|
||||
[](https://infiplot.com)
|
||||
[](https://infiplot.com)
|
||||
[](LICENSE)
|
||||
[](https://linux.do)
|
||||
|
||||
@@ -69,28 +69,6 @@ After deploy, fill in the environment variables — see the [Configuration guide
|
||||
|
||||
---
|
||||
|
||||
## Team & Vision
|
||||
|
||||
We're a group of young people from Tsinghua University and other schools.
|
||||
|
||||
On one hand, we're longtime, devoted players of galgames, otome games, FMV, and AI role-play games. Even while enjoying them, we kept imagining how much more delightful and thrilling it would be if the story choices weren't fixed in advance — or if you could truly interact with an AI character in depth, instead of just texting it through a chat app.
|
||||
|
||||
On the other hand, we happen to know a little about large-model technology: enough to turn ideas into working software quickly with AI, and to have formed some modest views on the technical paths available and the limits of what today's tech can build.
|
||||
|
||||
The spark came on April 22, 2026, when [@zan2434](https://x.com/zan2434) and others released [flipbook](https://flipbook.page/). We were stunned and delighted by this entirely new form of interaction.
|
||||
|
||||
So one day in May, we agreed on the spot to build something like this — both to help people live out the fantasies they'd once set aside, and to explore the new modes of interaction that multimodal models make possible.
|
||||
|
||||
The project is still very early and many features are far from polished. We'd love your feedback — open an [issue](https://github.com/zonghaoyuan/infiplot/issues), or join our dev team and explore the new possibilities with us, and satisfy your own curiosity.
|
||||
|
||||
Get in touch: hi@infiplot.com
|
||||
|
||||
Scan to join our **beta community on QQ** (group ID `575404333`) to share feedback and help shape the project:
|
||||
|
||||
<img src="apps/web/public/qq-group.webp" alt="InfiPlot beta community QQ group QR code" width="200" />
|
||||
|
||||
---
|
||||
|
||||
## How it works
|
||||
|
||||
Built on text, image, and audio models, we've assembled a multi-agent framework to deliver on InfiPlot's goal. We split the agents into five roles — **Architect, Writer, Character Designer, Cinematographer, and Painter** — that work together to keep the plot coherent, the characters consistent, and the scenes continuous, all while making the story as compelling as we can.
|
||||
@@ -122,6 +100,28 @@ There is no traditional game UI baked into the art. The AI paints the world in w
|
||||
|
||||
---
|
||||
|
||||
## Team & Vision
|
||||
|
||||
We're a group of young people from Tsinghua University and other schools.
|
||||
|
||||
On one hand, we're longtime, devoted players of galgames, otome games, FMV, and AI role-play games. Even while enjoying them, we kept imagining how much more delightful and thrilling it would be if the story choices weren't fixed in advance — or if you could truly interact with an AI character in depth, instead of just texting it through a chat app.
|
||||
|
||||
On the other hand, we happen to know a little about large-model technology: enough to turn ideas into working software quickly with AI, and to have formed some modest views on the technical paths available and the limits of what today's tech can build.
|
||||
|
||||
The spark came on April 22, 2026, when [@zan2434](https://x.com/zan2434) and others released [flipbook](https://flipbook.page/). We were stunned and delighted by this entirely new form of interaction.
|
||||
|
||||
So one day in May, we agreed on the spot to build something like this — both to help people live out the fantasies they'd once set aside, and to explore the new modes of interaction that multimodal models make possible.
|
||||
|
||||
The project is still very early and many features are far from polished. We'd love your feedback — open an [issue](https://github.com/zonghaoyuan/infiplot/issues), or join our dev team and explore the new possibilities with us, and satisfy your own curiosity.
|
||||
|
||||
Get in touch: hi@infiplot.com
|
||||
|
||||
Scan to join our **beta community on QQ** (group ID `575404333`) to share feedback and help shape the project:
|
||||
|
||||
<img src="apps/web/public/qq-group.webp" alt="InfiPlot beta community QQ group QR code" width="200" />
|
||||
|
||||
---
|
||||
|
||||
## Configuration guide
|
||||
|
||||
InfiPlot talks to four kinds of model providers. **Text and Vision use any OpenAI-compatible endpoint**, so you can mix and match freely. **Image** currently goes to **Runware** (its own task-array protocol, not OpenAI-compatible). **TTS** uses **Xiaomi MiMo**'s own voice design / clone protocol — per-character voice design, clone, and per-line delivery direction.
|
||||
|
||||
Reference in New Issue
Block a user