How rasyaakbar/staticwebbuilder works
Project type and purpose
• This is a Next.js-based, frontend-only static site “Web Builder.”
• It exposes a visual funnel/page editor UI (no backend). You build and export static pages.
File structure
• Top-level config & tooling
• next.config.ts, tsconfig.json, tailwind.config.ts, eslint.config.mjs, package.json
• .github/workflows/nextjs.yml handles CI/CD for static deploy
• Public assets
• public/assets → hosted statically
• Next.js “app” folder (App Router)
• src/app/layout.tsx, page.tsx and global CSS
• src/app/_components → visual editor sub-system
• Reusable UI library
• src/components/ui → buttons, dialogs, forms, etc.
• src/components/loading.tsx
• State & behavior
• src/providers/editor → React context, editor-actions, provider component
• src/hooks/use-mobile.tsx → viewport detection
• Utilities & types
• src/lib/constants.ts, types.ts, utils.ts
README for additional insights
• “Modifying Web Builder to work without the backend, only deploying Front-end part. Very useful to build static website.”
• Confirms static-only, no data persists server-side. All state lives in client memory or is downloaded/uploaded by the user.