How favger/layerhub-io works
Project type and purpose
• This is a frontend-centric monorepo (managed by pnpm/turborepo) that provides a core “canvas & design engine,” object definitions, download utilities, and React/Vue wrappers, together with three demo applications (Next.js, React SPA, Vue SPA). Its purpose is to enable interactive design editing (graphics, text, video, presentation) in multiple frameworks.
File structure
• Top-level: pnpm-workspace.yaml, turbo.json, lockfiles – defines a monorepo.
• packages/
• core: the rendering & editing engine (controllers, parsers, state, utils)
• objects: a library of static object classes (Background, Image, Text, Video, etc.)
• downloader: asset-download utility
• react: React bindings for core (hooks, context, canvas component)
• vue: Vue plugin/wrapper for core
• types: shared TypeScript definitions
• apps/
• next-editor: Next.js demo with SSR/CSR pages, API route, custom components, contexts & hooks
• react-editor: React SPA demo (webpack + Nginx config), Redux store slices for editor state, services (Pixabay, Pexels)
• vue-editor: Vue 3 SPA demo (Vite config), single-file components (App.vue, Editor.vue)
README
• Confirms a monorepo setup: “pnpm i”, “pnpm build”, “pnpm dev” per app.
• No backend or database – purely client libraries & example apps.