Lohnt sich dein eigenes Workelo?

Build a self-hosted employee onboarding and offboarding tracker. Empty folder, no scaffolding questions, just build it.

Stack, non negotiable: Next.js 15 with the App Router and TypeScript, SQLite through Prisma, Tailwind for styling, server actions for all mutations. No external auth provider. No telemetry. No analytics.

Data model:
- Journey template: name, type (onboarding, crossboarding, offboarding), list of TaskTemplates.
- TaskTemplate: title, description (markdown), owner role (manager, hr, it, employee), dayOffset (integer, negative means before the start or exit date), optional link.
- Employee: name, personal email, work email, role, manager name, manager email, startDate, exitDate (nullable), status.
- Journey: created by applying a template to an employee, snapshots the tasks so later template edits do not rewrite history.
- Task: title, description, ownerEmail resolved at launch, dueDate computed from dayOffset plus the anchor date, done flag, completedAt.

Features in scope:
- CRUD for templates with a drag free ordering (just an integer sort field and up/down buttons).
- Launch a journey: pick employee plus template, preview computed due dates, confirm.
- Dashboard: all active journeys, percent complete, overdue count, sorted by nearest due date.
- Per journey view grouped by week relative to the anchor date, checkboxes that complete tasks via server actions.
- A tokenized public task page at /me/[token] so a new hire or manager can see and tick their own tasks without an account. Token is a random 32 char string on the journey, unguessable, no login.
- A daily digest script (npm run digest) that finds tasks due or overdue and emails each owner one summary. Use nodemailer with SMTP_HOST, SMTP_USER, SMTP_PASS, MAIL_FROM from .env. If those are unset, print the emails to stdout instead of failing.
- Seed script with one realistic onboarding template (about 15 tasks spanning day -7 to day +30) and one offboarding template (about 10 tasks).

Explicitly out of scope: HRIS or ATS integrations, Slack or Google Workspace provisioning, e-signature, file uploads, multi tenancy, role based admin permissions. One admin, protected by a single ADMIN_PASSWORD in .env checked in middleware with a cookie. That is enough.

Deliver a README with setup, .env.example, prisma migrate command, and a cron line for the digest. Make the /me pages look decent on a phone; that is the only surface an employee ever sees.