How atothey/fileflex works
Project type and purpose
• This is a Next.js-based web application whose primary function is in-browser file handling and conversion (using ffmpeg.wasm). It combines server-side rendering (SSR) for initial page loads with a client-heavy React component library for the interactive UI. It’s containerized via Docker and orchestrated (locally) via docker-compose.
File structure
• Top-level configuration:
• .eslintrc.json, tsconfig.json, next.config.js, tailwind.config.js(.ts), postcss.config.js, Dockerfile, docker-compose.yml
• App entrypoint (Next.js “app” directory):
• app/layout.tsx, app/page.tsx, app/globals.css
• Shared UI components (components/ & components/ui/):
• Dropzone, Navbar, ModeToggle, ThemeProvider, plus building-block UI (button, select, tabs, toast, skeleton, badge, sheet)
• Utilities (utils/ & utils.ts):
• Localization (locales/):
• ar.json, en.json, fr.json
• Public assets (public/images)
• Build metadata (package.json, components.json)
README
• No content in README.md; rely on file structure and naming conventions to infer architectural intent.
Elements
• Sub-blocks inside each: under Browser: React components, i18n, wasm engine; under Server: Next.js routing, static asset host
• Browser → Server (HTTP fetch)
• Browser → Wasm Module (load/execution)
• Blue for client components
• Green for server-side components
• Grey for infrastructure (Docker)
• Purple for external libs (ffmpeg.wasm)