mesh-avatar-studio
Turn one illustration into an animated 2D mesh avatar with a coding agent and a local editor
A free, real-time canvas for diagrams, whiteboards, mind maps, infographics and documents. Built for teams who think visually.
DesignTypeScript · MDXGitHub @livediagram-appOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
livediagram.app mono repo. Containing frontend and backend code.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A collaborative diagram editor that works without signing in. Open a link, draw, share. Real-time presence, cursors, comments, undo and redo. The canvas never sits behind an auth wall, so the friction to start is "open the link, start drawing."
Live at livediagram.app. MIT-licensed and self-hostable end-to-end.
• Marketing at / is the pitch and feature tour.
• Editor is the canvas, served at clean routes (/new, /document/, /explorer/...; no /live prefix). Guests get a per-browser identity and full persistence; signed-in users get the saRead the full README ↗The monorepo for liveworkspace and its products, livediagram, liveplanner, livedocuments and livedesign, plus what they share.
packages/ shared by every product (@liveworkspace/*)
liveworkspace/ the platform: the liveworkspace.app site, its services (accounts, index, drive, media,
community, telemetry, status), the migrate tool, and its specs (liveworkspace/docs/specs)
livediagram/ livediagram.app
liveplanner/ liveplanner.app
livedocuments/ livedocuments.app: articles, slides and infographics
livedesign/ livedesign.app: logos, wireframes and photos
docs/ how this repo is laid out, CI and deploys, and the move from the historical livediagram.app
Read docs/structure.md first: it covers what's shared, what each product keeps, and the order the sharing was done in.
Every product and the platform keeps its specs and blueprints in its own docs/specs/
(liveworkspace's are liveworkspace/docs/specs). A change updates the
spec first, then the blueprint, then the code.
One pnpm workspace and one lockfile, at the root. Node 22+, pnpm via corepack.
corepack pnpm install
corepack pnpm dev:diagram # livediagram's apps
corepack pnpm dev:planner # liveplanner's apps
corepack pnpm dev:documents # livedocuments' apps, on the 33xx ports
corepack pnpm dev:design # livedesign's apps, on the 34xx ports
corepack pnpm dev:workspace # liveworkspace.app on :3000, with its seven services behind it
corepack pnpm dev:site # liveworkspace.app's pages alone on :3000
corepack pnpm dev:accounts # the accounts API alone on :8787
corepack pnpm dev:telemetry # the telemetry API alone on :8790
corepack pnpm dev:community # the Community API alone on :8791
corepack pnpm dev:media # the media API alone on :8792
corepack pnpm dev:index # the index API (One Explorer) alone on :8793
corepack pnpm dev:status # the status Worker alone on :3010
corepack pnpm dev:drive # the Google Drive mirror alone on :3011
corepack pnpm typecheck # everything; or inside a product folder, just that product
Each product folder keeps its own scripts (cd livediagram && corepack pnpm test runs only
livediagram's tests), its own docs, and its own AGENTS.md for product-specific rules. The lint,
format, test and Next.js settings are shared (packages/oxlint-config, prettier-config,
vitest-config, next-config), so a rule changes once for every product.
Every product deploys from here, from the root .github/, to the liveworkspace Cloudflare account
each wrangler.toml pins. Staging follows main, and production is a manual gate that ships what
staging runs. A deploy builds and ships only the Workers a change reaches. The products' own
.github/ folders are inert. docs/ci.md has the details.