Skip to content

Company Website · Public Site + Admin CMS

Alphinex Solutions — Website & Admin CMS

I built the CMS side of the Alphinex Solutions website for my employer in about a week: MongoDB data layer, Cloudflare R2 with private CVs, an upload-time image cropper, an admin panel and structured data for search.

  • The live Alphinex Solutions homepage leads with a 24-hour website delivery pitch, an email capture and key delivery stats.
  • The live services page lays out each offering as a card with its feature checklist and a link to a dedicated detail page.
  • In the admin dashboard, portfolio projects are managed as cards with cover images and reordered by drag and drop. Demo data.
  • Job applications are reviewed per opening, with status tracking, a cover letter and short-lived signed links to the private CV. Demo data.
  • Every image upload in the admin passes through a built-in cropper that locks the aspect ratio before the file is stored. Demo data.
On this page

My role

This is the company website and admin CMS I built for my employer, Alphinex Solutions, and delivered in about a week. Two developers worked on the codebase. The public pages and a first admin panel came first. My share was making it something the company can operate by itself. That covered the switch to MongoDB, Cloudflare R2 storage, image handling, a storage manager, settings, SEO work and error states throughout the admin. The stack is Next.js 14 with the App Router, TypeScript and Tailwind CSS. It is live at alphinex.com.

The problem

A company that sells software has a website that is its first piece of work a prospect sees, so it has to be quick, rank in search and show current projects, people and open roles. The people running the company needed to keep all of that fresh without waiting for a developer. The existing version had the right pages but hard-to-run content: edits meant code changes, CVs would sit at public URLs, uploaded images broke grids, and a failed request in the admin looked exactly like an empty list.

Key decisions and why

Move from Postgres to MongoDB

The site started on Prisma over hosted Postgres. I switched it to MongoDB and Mongoose in a single pass, with nine models sharing one set of base options and a connection cached to survive hot reloads and serverless cold starts. The reason was operational. Collections and indexes appear on first write, so setting up a new environment means a connection string plus a seed script and nothing else. Given a week, removing steps was worth more than relational features the site did not use.

Private CVs by default

CVs hold personal data. The public form can upload one, but nobody can browse to it. Opening an application in the admin produces a signed link that stops working after five minutes. The upload check accepts either the reported MIME type or the extension, since browsers disagree on how they label PDF and Word files.

Fix images at upload, not at display

Every admin image upload passes through a cropper before storage. It locks the aspect ratio per slot (16:9 for projects, a round mask for team photos), allows drag and zoom, and exports JPEGs no wider than 1600 px. Multiple files queue up ("3 images left to crop"). Doing this once at upload keeps public grids aligned and stops pages loading oversized originals.

Make failure visible

Each admin list has its own error state and a Retry button, and deletes ask first. A failed load must not look like an empty table, since that tempts someone to type the content in again.

What I built

  • Content: projects, team and testimonials with drag-and-drop ordering saved to the database, blog posts with Markdown bodies and a published switch, and job openings with an applicant count.
  • Applications: contact details, links, cover letter and private CV per applicant, each moving through pending, reviewed, shortlisted or rejected.
  • Storage manager: R2 usage against a quota, files grouped by folder, bulk delete and signed previews of private files.
  • Contact and settings: who receives contact-form mail (sent via Resend or SMTP), with a test button, password change and the site-wide consultation link behind every consultation button.
  • Search: per-page titles, descriptions and Open Graph tags, a sitemap and robots file, and JSON-LD for the organization, services, job postings, posts, breadcrumbs and reviews.

Auth is NextAuth with credentials and middleware over every admin route. In total the site is roughly 14,000 lines of TypeScript with 25 pages and 25 API routes.

Results

  • Staff update the project list, team page, reviews, articles, openings and consultation link themselves.
  • Jobs are posted and candidates apply online, with CVs staying private.
  • Layouts stay clean because images are cropped to their slot when uploaded.
  • Usage, quota and clean-up of media are visible in the admin.
All projects

Have a project in mind?

Whether it's an MVP, a dashboard, or a rescue mission on an existing codebase — let's talk about it.

Prefer to talk first? Book a free 30-min call (opens in a new tab)