Do Siki 30f0b94a2f chore: migrate from Linear to Plane MCP, add .agent/ framework
- Add .agent/ directory with AGENTS.md, steering docs, workflows, references
- Replace CLAUDE.md with slim reference pointing to .agent/
- Migrate TODO.md from Linear ZEE-* to Plane MITHOME-* identifiers (26 issues synced)
- Add .mcp.json.example with Plane MCP server config
- Remove .agents/, .cursor/, .roo/ legacy directories
- Update .gitignore: add .mcp.json, remove old IDE dirs
- Replace linear-sync.js approach with Plane MCP server (@makeplane/plane-mcp-server)
2026-04-26 21:25:39 +02:00

mozdIT Bt. Website Development

CI/CD Pipeline Docker Linear Sync Deployment

Modern Next.js 14 website for mozdIT Bt. - Hungarian IT services company specializing in web hosting, email services, and DNS administration.

🚀 Quick Start

# Development server
cd proto && npm run dev

# Docker development environment  
docker-compose -f docker-compose.dev.yml up -d

# Run tests
cd proto && npm run test:all

🔄 Dual Sync Architecture

This project uses separated sync systems for optimal management:

🧪 Linear Sync (Test Management)

🐙 GitHub Sync (CI/CD)

  • Code Versioning: Git-based source control
  • CI/CD Pipeline: Automated testing and deployment
  • Docker Integration: Container build and registry
  • Deployment: Staging and production via Dokploy

🧪 Test Types

  • Unit Tests: Component and logic testing
  • Browser Integration: jsdom + mocked APIs
  • Docker Integration: Real HTTP calls to services
  • E2E Tests: Complete user workflows

🛠️ Tech Stack

  • Frontend: Next.js 14, TypeScript, Tailwind CSS 4
  • Design System: CSS Variables, Dark Mode, Custom Animations
  • Content Management: JSON-based structured content
  • Backend: Next.js API Routes, MongoDB
  • Testing: Jest, React Testing Library, Docker
  • Deployment: Dokploy, Docker
  • Monitoring: Winston, Loki, Grafana
  • Project Management: Linear, GitHub Issues

📈 Current Status

Requirements Coverage Test Automation Build Status

Completed Features

  • Responsive website with modern design
  • Design System with CSS variables, animations, and micro-interactions
  • Dark Mode with system preference detection and manual toggle
  • JSON Content Management - Structured, easily modifiable content system
  • Contact form with validation & spam protection
  • Rate limiting and security features
  • Docker development environment
  • Comprehensive test suite
  • CI/CD pipeline with Linear integration
  • Requirements traceability system

🚧 In Progress

  • Performance optimization (ZEE-44)
  • SEO enhancements
  • Analytics integration

📚 Documentation

Sync Systems:

Development:

🎨 Design System

The project uses a comprehensive design system with:

  • CSS Variables: Brand colors, spacing, shadows, transitions
  • Dark Mode: Automatic system preference + manual toggle via ThemeProvider
  • Animations: fadeIn, float, pulse, hover effects (lift, scale, glow)
  • Components: Buttons, cards, icons with consistent styling

📝 Content Management

All website text content is managed through JSON files:

proto/src/content/
├── types.ts          # TypeScript definitions
├── index.ts          # Content loader utility
├── common.json       # Shared texts (buttons, labels)
└── pages/
    ├── home.json     # Homepage content
    ├── about.json    # About page content
    ├── services.json # Services page content
    └── contact.json  # Contact page content

Usage:

import { content, getPageContent } from '@/content'

// Access content
const aboutContent = content.pages.about
const servicesContent = getPageContent('services')
S
Description
No description provided
Readme MIT
2.5 MiB
Languages
TypeScript 60.3%
JavaScript 24.8%
HTML 7%
Shell 4.4%
CSS 3%
Other 0.4%