🚁 UAV Website

A modern web application for presenting UAV projects, vehicles, competitions, and sponsors.

Built with Next.js, React, Prisma ORM and Tailwind CSS. Made for Dumlupinar University Kuasar UAV Team.

Status: This project has successfully fulfilled its original goals for the Dumlupinar University Kuasar UAV Team.

✨ Features

• ⚡ Next.js App Router for modern, file-based routing
• 🎨 Tailwind CSS for responsive, utility-first styling
• 🧱 (Optional) shadcn/ui components for a consistent UI layer
• 🗄 Prisma ORM with PostgreSQL (running in Docker)
• 📱 Fully responsive layout (mobile, tablet, desktop)
• Structured sections for:
  • Home
  • Vehicles
  • Competitions
  • Sponsors
  • Contact

🧰 Tech Stack

• Next.js
• React
• TypeScript
• Tailwind CSS
• Prisma ORM
• PostgreSQL (via Docker)
• shadcn/ui (if used in components)
• next/font
  (currently using the default font configuration)

Database Diagram

🖼 Screenshots

🚀 Getting Started

You can run the project locally using the steps below.

1. Clone the repository

git clone <repository-url>
cd <project-folder>

1. Install dependencies

npm install
# or
pnpm install
# or
yarn
# or
bun install

1. Run PostgreSQL with Docker

Make sure you have Docker installed and running, then start a PostgreSQL container (or use your existing setup).

Example (adjust values as needed):

docker run --name ihadb -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres \
  -e POSTGRES_DB=ihadb -p 5432:5432 -d postgres

Set your DATABASE_URL in .env:

DATABASE_URL="postgresql://postgres:postgres@localhost:5432/ihadb"

Run Prisma migrations (if applicable):

npx prisma migrate deploy
# or
npx prisma migrate dev

4. Start the development server

npm run dev
# or
pnpm dev
# or
yarn dev
# or
bun dev

Then open:

👉 http://localhost:3000

⚙️ Configuration Notes

Some behavior depends on configuration files:

• app/robots.ts Controls how search engines see and index the site. To make the site publicly visible in search engines, this file must be adjusted.

• middleware.ts Handles features such as authentication, route protection, or redirects. This file needs to be properly configured before any real production use.

• Fonts The project currently uses the default font configuration via next/font. If you want a specific font family, you will need to update that configuration.

🛣️ Future Improvements

The following items can be considered as a roadmap for future development:

Account management improvements

• Connect the existing account deletion button to backend logic and safely support full account removal.

Search engine visibility and SEO improvements

• Update app/robots.ts to allow search engines to crawl public pages.
• Review next.config.ts headers and remove or scope X-Robots-Tag rules to admin-only routes.
• Expand page metadata in layout.tsx (or _document.tsx) with title, description, keywords, and Open Graph fields.
• Add an app/sitemap.ts file to expose core URLs for indexing.
• Add descriptive alt text to all image components.
• Keep semantic heading order (h1 → h2 → h3) and use a single h1 per page.
• Keep URL paths SEO friendly when introducing new routes.
• Validate performance and mobile usability with Lighthouse, and optimize image delivery with Next.js Image Optimization.
• Add Schema.org JSON-LD organization metadata in layout.tsx.

Typography and visual identity

• Introduce a custom typography system if a dedicated font family is preferred.

Middleware hardening

• Finalize middleware.ts configuration for authentication, protected routes, and redirect behavior.

Multi-admin support

• Extend authentication and database schema to support multiple admin accounts.

🌍 Deployment

The app was designed to be deployable on platforms like Vercel or similar.

Typical flow:

• Push the repository to GitHub / GitLab.

• Connect the repo to a hosting platform (e.g. Vercel).

• Configure environment variables (e.g. DATABASE_URL).

• Ensure your PostgreSQL instance (Docker / managed DB) is reachable.

• Trigger a build & deploy.

For more details, refer to the Next.js deployment docs.

📌 Project Status

• This project was created for the Dumlupinar University Kuasar UAV Team and has fulfilled its main purpose.

• The repository is kept mainly for reference, portfolio, and learning purposes.

• If you clone or extend it for your own needs, feel free to adapt the stack, design, and logic as you like.