Telente Technologies
The public site and content platform for a software agency — a React front end over an Express and MySQL admin backend managing services, projects, blogs, team, careers and testimonials.
- 7
- Managed content types
- 9
- Admin controllers
- 12
- Public pages
- Live
- In production
- Role
- Author
- Year
- 2026
- Status
- Live
- Type
- Agency site & admin platform
01Overview
Telente Technologies is a software engineering agency in Okitipupa, Nigeria. This is its website and the admin platform behind it: a React and Vite front end for the public site, and a Node, Express and MySQL backend that powers every piece of content on it.
Nothing on the public site is hardcoded. Services, projects, blog posts, team profiles, careers, testimonials and contact submissions are all managed through a secure admin portal, which is what separates a company website from a company brochure.
It runs in production: the site at telente.site, the API and uploads on their own subdomain.
02The problem
Agency sites decay. The team page lists someone who left a year ago, the careers page advertises a closed role, and the case studies stop at whatever was shipped when the site was built — because every change requires a developer and a deploy.
The usual fix is a hosted CMS, which trades the deploy problem for a vendor, a monthly cost and a content model that never quite fits.
The second requirement is discovery. An agency site that does not rank for what the agency does is an expensive business card, so SEO could not be an afterthought bolted on at the end.
03Architecture
- 01
Content as data
Services, projects, blogs, team, careers, testimonials and contact submissions each have a model and an admin surface. Publishing is a database write, not a pull request.
- 02
Separate API and uploads origin
The API and uploaded media are served from their own subdomain rather than from the site, keeping the static front end independently deployable.
- 03
Secure admin portal
Authenticated content management with nine controllers covering the editable surfaces, kept behind its own auth boundary rather than mixed into the public routes.
- 04
Configuration through environment
Every deployment-specific value is an environment variable, so the same build runs locally and in production without code changes or committed secrets.
04Key decisions
Own the CMS rather than rent one
The content model is small and specific — an agency's services, work and people. Building it directly costs less than fitting it into a general-purpose CMS and removes a recurring bill and a vendor from the critical path of the company's own website.
SEO as a project goal, not a checklist
The site was structured around what the agency needs to be found for. Treating discovery as an architectural requirement rather than a set of meta tags added late is the difference between ranking and merely being indexed.
Contact submissions persisted, not emailed
An enquiry that only exists as an email is an enquiry that gets lost. Storing them means the agency can see what it has not answered.
05Stack
- React
- Vite
- TypeScript
- Node.js
- Express
- MySQL