How arshiapazoki/codefolio works
Project type and purpose
• This is a Next.js 13 front-end application (no dedicated backend code or database).
• It appears to be an interactive, component-driven site (possibly a portfolio or dashboard UI), built using the App Router, feature modules, shared libraries, and custom “widgets.”
• It is intended to be deployed server-side (SSR/SSG) on a PaaS (e.g., Vercel or Liara).
File structure
• Top level:
• next.config.ts, tsconfig.json, eslint.config.mjs, postcss.config.mjs — build and lint configs
• liara.json — deployment config
• tree.js — utility script (generates file listings?)
• src/app/ — Next.js App Router: global layout, head, route groups (home/, timeline/)
• src/features/ — feature-based modules, each with:
• lib/ — hooks or helper functions
• model/ — data-fetching or state hooks
• ui/ — presentational React components
• src/shared/ — cross-feature utilities:
• configs/ — static JSON or TS config data
• lib/ — shared hooks (e.g., time-based)
• src/widgets/ — reusable UI “widget” components (ActivityBar, CodeEditor, Explorer, etc.)
README for additional insights
• Bootstrapped with create-next-app using the new App Router.
• Uses next/font for automatic font optimization.
• No mention of backend or database—this is a purely frontend/SSR site.
• Deployment target: Vercel (but Liara config is present).