Jova Software

The content API behind the company website: profile, specialities, portfolio, clients, team and articles, with visit tracking.

Type
Internal and SaaS
Stack
Laravel
Role
Backend developer.

The problem

Website content lived in the page templates, so every copy change needed a developer and a deploy.

What I decided

  1. Moved all public content behind one read API with an authenticated admin, so editors change text without touching the site.
  2. Recorded visits and a checking date per request, which gave the company its first view of what visitors read.

Where it landed

The website reads from the API, and content changes no longer wait for a release.

All projectsNext project: Jova Resto

Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.