Tavotto
AI drew your research figure. Tavotto makes it publication-ready: edit matplotlib figures on a canvas, lay out in mm, check journal rules. Free, open source.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證livediagram.app mono repo. Containing frontend and backend code.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
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 sa檢視完整 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.