A Next.js portfolio and blog with optional Notion CMS integration, i18n (en/fr), and local Markdown articles.

• Next.js 16 – React framework
• React 19
• Tailwind CSS 4 + DaisyUI
• next-i18next – i18n (en/fr)
• Notion API – optional CMS (feature-flagged)
• Framer Motion – animations
• Zod – schema validation
• Jest + Cypress – tests

• Node.js 24.x (see .nvmrc)
• Yarn or npm

# Install dependencies
yarn install
# or: npm install

# Run development server
yarn dev
# or: npm run dev

Open http://localhost:3000.

Production is the master branch (prod = master). Everything below assumes that.

1. Base branch for new work: dev

   • Create feature branches from dev, not from master.

2. Feature work

   • Branch from dev:
     git checkout dev && git pull && git checkout -b feature/your-feature
   • Commit and push to feature/your-feature.
   • Open a PR into dev. Merge after review/tests.

3. Releases

   • Branch from dev:
     git checkout dev && git pull && git checkout -b release/1.0.2
   • Bump version in package.json, update changelog if you have one, fix any release-blocking bugs.
   • Run tests and build:
     yarn test:ci && yarn build
   • Open a PR into master (or merge when ready).
   • Tag after merge:
     git checkout master && git pull && git tag v1.0.2 && git push origin v1.0.2
     (Do not push if you prefer to tag later.)

4. Hotfixes (production-only fixes)

   • Branch from master:
     git checkout master && git pull && git checkout -b hotfix/short-fix
   • Fix, test, then merge into master (and optionally into dev so history stays aligned).

5. Do not

   • Put platform-specific binaries (e.g. @next/swc-win32-x64-msvc) in dependencies; Next.js installs the right SWC via optionalDependencies.
   • Merge directly to master from feature branches; use dev → release/* → master.
   • Force-push to master.

Brahim Abdelli – brahimabdelli

The project can be deployed on Vercel or any Node-friendly host. Ensure NODE_VERSION or .nvmrc is set to 24 if required by the platform.