Recent work01Frontend EngineerOct 2026 – PresentRemote · Lagos, Nigeria
IntelSprings
Experiential learning platform
Private beta · walkthrough on request
- Product
- Practice-first learning for finance and business professions
- Apps
- Learner, instructor, institution admin, staff console
- My focus
- Session layer, course builder, certificates, release path
- Ownership
- Sole frontend engineer
- Status
- In development, pre-launch
- Stack
- Next.js 16
- React 19
- TypeScript
- Turborepo
- Tailwind CSS 4
- TanStack Query
- dnd-kit
- Tiptap
- Docker
The product
IntelSprings teaches by doing. Every lesson follows the same five-stage loop: do, reflect, learn, reinforce, transfer. Learners work through a real task first and meet the theory after. Courses are organised by discipline, course, level and lesson, and each level ends in an assessment gate and a verifiable certificate.
The frontend is a Turborepo of four Next.js apps: the learner app, the instructor app with its course builder, an institution admin console and an internal staff console. They share UI, API-client, query and security packages. The platform is in active development against a test backend and has not launched.
My role
I handle the IntelSprings frontend on my own, across all four apps, from the shared platform and session layer to the course builder and the release pipeline.
A session layer the browser never sees
The browser never talks to the backend directly. Each app has one catch-all API route that proxies every call.
Tokens live in httpOnly cookies
On sign-in the proxy moves the access and refresh tokens out of the response body and into httpOnly cookies, so no page script can read them. On the way out it adds the bearer token from the cookie.
Safe failures
A 401 clears the session cookies. Error responses are stripped of the backend's internal exception details before they reach the browser. State-changing requests must come from the app's own pages.
Refresh before expiry, once
Tokens are refreshed when less than a minute remains, rather than retried after a 401, because an upload body cannot be sent twice. Parallel requests share a single refresh call, which matters because the backend rotates the refresh token on every use.
Private by default
A shared proxy sends signed-out visitors to sign-in before a page renders, using an allow-list of public paths, so a newly added route is private unless someone says otherwise. Security headers and the Content-Security-Policy come from one shared builder.
Course builder
Instructors build a course step by step: setup, structure, an editor for each stage of each lesson, then review and publish.
Rules enforced in code
Lesson content is validated by zod schemas, and the course rules (lessons per level, the minimum number of gate and drill questions, the minimum length of reflection prompts) are checked before publishing, not left to reviewers.
Accessible drag and drop
Levels and lessons are reordered with dnd-kit, using both pointer and keyboard sensors. Screen-reader announcements use item names rather than ids, and the motion respects reduced-motion settings.
A constrained rich-text editor
The theory editor is Tiptap, limited to an agreed set of elements, with custom nodes for media (with alt text and transcript) and formulas, so content stays consistent across courses.
Autosave that does not lose work
Edits save after a short pause, with only one save in flight at a time. The builder saves when the instructor leaves the page and keeps failed edits so they can be retried.
Certificates, design system and release path
Verifiable certificates
The certificate QR code is rendered on the server as a single SVG path: no client JavaScript, and sharp when printed. The public verification page has verified and pending states and structured data, and only verified certificates can be indexed.
Tokens, not colours
Components use semantic token names only, and each app supplies its own values, so the four apps share every component while keeping their own look.
One image recipe for four apps
A multi-stage Dockerfile prunes the monorepo down to the chosen app, installs from a cached store, builds Next.js in standalone mode and ships a small Node runtime. A publish script pushes images tagged by stage and commit, and the API address is read at runtime instead of being baked in.
Quality gates on every commit
Pre-commit hooks lint the staged files and type-check only the apps that changed. Lint includes accessibility rules and fails on any warning.
Where integration-status started
The integration-status tool described on this site was first built here, to track which screens were wired to the test backend and what each blocked screen was waiting on.