Back to archive
IV. Client Builds & Logistics Platformssupportingcontributor

SupaNext — Catalog Back-office

"SupaNext" — a Next.js + Supabase admin / e-commerce back-office: catalog (products/categories/banners/news/sales) with RBAC (roles/permissions), data-table + charts, multilingual (Languine + next-intl, en/ru/uz) and domain-based localization. The user's contribution is Supabase auth/client integration.

Status
maintained
Period
2025-03-28 → 2025-08-12
AI sessions
Stack
Languages
TypeScript
Frameworks · Infra
Next.jsSupabaseshadcn/uinext-intldnd-kit
§01

Overview

  • What it is: An admin panel / back-office on Next.js + Supabase (code name in package.json — supanext). Manages products, categories, banners, news, sales with a role model (roles/permissions/roles-permissions). Route groups (public)/(auth)/(admin), dashboard with charts/data-table/sidebar (shadcn). Multilingual + domain-based localization (nginx). The purpose of "whieda" — likely a specific client/brand (to be clarified).
  • Type / status / role: web-app (admin / e-commerce back-office) · maintained · contributor — the user has 9 commits (Supabase plumbing), main author is Nuriddinkhuja (24).
  • Activity period: 2025-03-28 → 2025-08-12 (~4.5 months), 36 commits.
§02

Stack

  • Next.js (App Router, [locale], route groups public/auth/admin) + Supabase (@supabase/ssr, auth-helpers, storage), shadcn/ui (Radix, data-table, charts, sidebar), dnd-kit (sorting), react-hook-form.
  • i18n: Languine (AI translation, languine.json → en→ru/uz) + next-intl (messages/[locale].json), domain-based localization (docs/domain-localization*.md, nginx config).
  • Infra: Bun, middleware (auth/session), scripts/ (setup-admin, storage), api/supabase + setup-storage.
§03

Technical challenges

Confirmed by the user's commits:

  • Supabase client unification (getSupabaseClient factory across all modules): eliminating init duplication, single access pattern. → refactor toward consistency on a mid-size codebase.
  • Auth via `getClaims` + session in middleware (cookie handling, SSR sessions): correct server-side management of Supabase sessions in Next middleware. → knowledge of Supabase SSR authentication (a non-trivial topic).
  • RBAC back-office (roles/permissions/roles-permissions modules) — a team feature, partially touched by the user.
  • AI localization (Languine): automatic translation of messages en→ru/uz. → modern i18n tooling.
§04

AI-assisted development

  • Sessions found: 0. The repo has .cursor/ — Cursor was used.
  • What was done with AI: likely Cursor-assisted development; Languine — AI translation.
  • AI-workflow patterns: AI localization + Cursor; no Claude Code transcripts.
§05

Achievements & metrics

  • Supabase back-office with RBAC, catalog, charts/data-table, multilingual (en/ru/uz) + domain-based localization.
  • The user's contribution: Supabase client unification + SSR sessions.
§06

Contributors

git shortlog · all branches

  1. Dave939
  2. Nuriddinkhuja24
  3. root3
3 contributors36 commits total
Currently

Open to Senior / Staff engineering roles and selective freelance — production AI, platform, and full-stack work.

Get in touch