Skip to content
All systems
LiveFlagshipMALULEKE-KS

MALULEKE-KS

This platform: a full-stack, database-backed portfolio whose every claim is enforced by real rules, tests and an audit trail.

  • Next.js
  • React
  • TypeScript
  • PostgreSQL
  • Prisma
  • Tailwind CSS
  • Vercel
  • PLpgSQL+3
View it liveView the source
Started
November 2025
Shipped
October 2026
Last push
4 weeks ago
Commits this year
259
maluleke-ks.vercel.app
MALULEKE-KS homepage

Written by AI from the repository · updated 7 weeks agoAI

The problem

A portfolio usually claims things. This one is built to prove them: the site you are reading is itself a full-stack, database-backed system, and every claim it makes is enforced somewhere real.

How it works

  • Next.js 16 (App Router, TypeScript strict) serves the public site, an admin panel and a versioned REST API from one codebase on Vercel.
  • PostgreSQL (Neon) with Prisma holds everything. Visitors read only through public views under a separate database role — unpublished, private or client-restricted rows are not filtered out by the page, they never reach it.
  • A daily scheduler runs the jobs: the GitHub sync that keeps this catalog current, data retention, and the figures shown on the home page.
  • The CV is generated on request as PDF and Word from the same records the site shows.
  • The AI guide answers questions from the site's own data, through the Vercel AI Gateway, read-only and behind feature flags.

Engineering decisions

  • Rules live in the database. Business rules — an inquiry starts as new, a system is never deleted, a client's work stays hidden until approved — are database constraints and triggers, not page logic. The platform counts them live on the home page.
  • Every admin change is audited by database triggers, not by code that a route could forget to call.
  • Nothing hardcoded. Limits, windows, copy, titles and photos are admin-editable data; growing lists are lookup tables.
  • Every database capability has an endpoint, enforced by a coverage test, and the API matches a written OpenAPI contract.
  • Admin sign-in is hand-rolled — signed session cookies with a per-admin version, and two-factor authentication on every write.

Built to be trusted

  • 41 migrations, all additive — a CI guard rejects anything destructive.
  • 46 test files: unit tests and integration tests against a real Postgres database.
  • Releases ship in reviewed batches, each closing its tracked issues.

Where it stands

Live in production and growing page by page — this systems catalog is part of the current redesign.

Evidence

What MALULEKE-KS claims, and the proof.

Each claim says what it proves and what it doesn’t, and opens the exact code serving this page. Planned work is labelled as planned.

PlannedReviewed 2 Oct 2026

The guide will learn from questions it can't answer

Specified, not built yet.

What it proves
It is specified and scheduled (roadmap V2 item 16).
What it doesn’t prove
Anything about today: the guide records no questions yet.

Activity

How it's moving.

26 weeks agothis week
commits in the last 26 weeks
157

Latest commits

  1. V2 closed: the tracker opens with the closing ledger, every work package at the status it reached; v2.0.0
  2. Agile, SDLC and DBLC lead the principles; the profile README rebuilt for every reader
  3. The floating guide button stays off the home page: it starts hidden and decides in the browser (the server-drawn copy outlived hydration)
  4. V2 is done — V2 polish until V3; the README is the owner's own profile README again
  5. Hero photos on a phone: asked for at about half the screen's pixels (they sit dimmed under a veil), so sharp phones take the 768 px version
  6. Speed pass: the name paints at once; hero photos sized for phones; GitHub on the core, mark and name only
  7. Owner alerts reach the owner again (addresses stored as one spelling, the waiting alert retried); the GitHub mark sits on the core and moves
  8. Orbit: the core is named — GitHub, where every commit lands; it opens the owner's GitHub

Can I measure visits?

Anonymous page-view counts (Vercel Analytics, no cookies) help me see what’s useful. Nothing is measured unless you say yes, and you can change this any time from the footer.