Skip to main content
Lab68 Dev Platform is a brutalist-inspired workspace for cross-functional product teams. The GitHub repository lab68dev/lab68dev-platform contains a Next.js 16 app that powers the hosted experience at lab68dev-platform-1ds5.vercel.app. This page covers the feature surface, technical architecture, and the steps required to run or extend the platform.

Product Highlights

  • Role-aware collaboration with workspace dashboards, kanban boards, files, meetings, wiki, diagrams, community threads, and AI utilities scoped by project permissions.
  • Nine-language localization pipeline backed by a unified translation registry with English fallbacks and automation scripts for consistency.
  • Theming and layout system that keeps the sidebar, header, and content regions responsive while supporting dark and light modes out of the box.
  • Mock authentication hooks that can be swapped for a production identity provider when you are ready to connect to external auth.
  • Developer marketing site that introduces Lab68’s mission, tech stack, and featured projects while linking to signup/login flows inside the app.

Live Experience Overview

The deployed site mirrors the repository’s App Router pages and adds top-of-funnel content:
  • Hero & Mission sections welcome builders, articulating Lab68’s focus on pragmatic tooling for shipping software.
  • Community CTA invites developers to join the GitHub organization, subscribe for updates, and explore highlighted initiatives such as AutoPR and Project Gamma.
  • Navigation shortcuts route visitors directly to login, signup, documentation, or project listings hosted by the Next.js application.

Tech Stack at a Glance

Repository Anatomy

The app/dashboard tree houses the productivity surface (projects, kanban, AI tools, meetings, files, wiki, community). API handlers like app/api/chat/route.ts provide edge-friendly endpoints for future automation.

Getting Started Locally

1

Install prerequisites

  • Node.js 18 or higher
  • pnpm 8 or higher (corepack enable is recommended)
2

Clone and install

3

Run the development server

Visit http://localhost:3000 to explore the workspace.
For a production build:

Environment Configuration

Set any secrets (API keys, analytics tokens, auth credentials) in a .env.local file before running pnpm dev or pnpm start. Next.js automatically loads values from this file in development. Avoid committing secrets to version control.

Localization Workflow

  1. English strings live in lib/i18n.ts as the base dictionary.
  2. Locale override files extend the base content; missing keys fall back to English automatically.
  3. Maintenance scripts such as restore_translations.js and fix_final_issues.js repair encoding issues and keep translations synchronized.
  4. To add a language, update the Language union, append a locale dictionary mirroring the existing shape, and rerun the restoration scripts if necessary.

Theming and Layout

The root layout (app/layout.tsx) wires a theme provider that tracks dark/light preference and propagates navigation chrome. Shared components in components/ (sidebar, topbar, cards, widgets) expose composable primitives so feature areas can reuse typography, spacing, and interaction patterns.

Feature Surface

Deployment Notes

  • The repository is Vercel-ready; connect the GitHub project to Vercel and select the default pnpm build command (pnpm build).
  • Ensure environment variables are configured in the Vercel dashboard before promoting to production.
  • For preview environments, Vercel will run pnpm install followed by pnpm build, mirroring local behavior.

Extending the Platform

  • Authentication: Replace the mock client utilities in lib/auth with calls to your chosen provider (Auth0, Clerk, custom OAuth). The existing RBAC checks will continue to work.
  • Translations: Use the scripts in scripts/ to backfill or sanitize locale data after bulk edits.
  • Custom Modules: Drop new feature routes under app/dashboard and reuse shared components for consistent UI.
  • Community Site: Update the landing copy or featured projects by editing the corresponding page sections within the App Router tree.