Skip to content
Nur Amin
← All projects
P-01Kembar Futagroup Corporate Site2026

Kembar Futagroup Group Site

A headless corporate site for an eight-unit group: Laravel and Filament hold every word, Nuxt renders it server-side, and the careers page runs on Odoo’s recruitment API.

My role
Sole developer — backend, admin panel, frontend, SEO layer and the Odoo integration.
Field
Web Development
Stack
  • Laravel
  • Filament
  • Nuxt 3
  • Vue
  • Tailwind CSS
  • MySQL
  • Spatie Media Library
  • Odoo API
Live: kembarfutagroup.co.id ↗Source private — client project

Overview

Kembar Futagroup is eight business units under one roof — foundry, construction, stone, agribusiness and more — and a group site has to speak for all of them without becoming eight sites. The public pages are Nuxt, rendered on the server; every string, image and meta tag they show comes from Laravel over an API. Nothing is hard-coded in the frontend, so the marketing team can change the group profile without a deploy.

The half nobody sees is the bigger half. Filament runs the whole content model: page blocks that can be reordered, articles, milestones, partners, leadership profiles and photo albums. Alongside it sit the operational tools — 301 redirects, a 404 log, a link checker that rebuilds its report from scratch on every run, and a Search Console sync that pulls daily metrics into the panel so the client sees traffic where they already work.

Recruitment started inside the panel and later moved to Odoo, where HR already worked. Vacancies are now pulled from Odoo every ten minutes into a shadow table, and every application is forwarded to an Odoo applicant card; the site keeps only a technical trace with a hashed email. The page renders from the copy, so Odoo being down stops updates, not the careers page. Odoo gives a reopened position a new id, so vacancies are matched on a hash of title, department and company instead — the URL already shared in WhatsApp groups stays alive.

Careers launched first, on the main domain, while the rest of the site waits for approval: nginx answers 503 everywhere except /karir. A subdomain would have been simpler on day one and would have moved every vacancy URL on launch day.

In pictures

Kembar Futa Group title card with a desktop mockup of the home page hero and a phone showing open vacancies.
FIG. 01Forest, saffron and cream with Plus Jakarta Sans. Mockups redrawn from the site with sample data; the site itself is in Indonesian.
Diagram: the Filament panel saves to a Laravel API, which serves JSON to Nuxt, which renders HTML for visitors and search engines; operational tools and MySQL sit beside it.
FIG. 02Every word comes from the panel; the frontend holds layout, not content.
Diagram: Odoo vacancies sync every ten minutes into a shadow table, Nuxt renders /karir from it, and applications are forwarded back to Odoo.
FIG. 03Odoo owns hiring; the site keeps stable vacancy URLs through an identity key.
Filament admin dashboard with form submissions, site status, action items, SEO health gauges and recent submissions.
FIG. 04One card, one question: colour appears only for status.
Three phone screens: the home hero with business units, the open vacancies list, and the application form.
FIG. 05Home, careers and the application form on a phone.

Function

Shape
Laravel 13 API-only + Filament 5 admin, Nuxt 3 SSR in front
Content
Pages, articles, business units, leadership, gallery — all editable
Careers
Vacancies synced from Odoo; applications forwarded to Odoo

What it does

  1. 01Page content assembled from reorderable blocks, edited entirely from the admin panel.
  2. 02Business units, leadership profiles, milestones, partners and company statistics as first-class content.
  3. 03Careers page fed by Odoo: vacancies synced every ten minutes, applications and CVs forwarded straight to Odoo.
  4. 04Stable vacancy URLs across Odoo reopenings, with slug and SEO meta owned by the site.
  5. 05Application form options read from Odoo, with each Odoo error mapped to a message the applicant can act on.
  6. 06Photo albums and a news section, both server-rendered for indexing.
  7. 07SEO metadata, redirects, a 404 log and a broken-link scanner, all managed in-panel.
  8. 08Google Search Console credentials, verification and daily metrics surfaced inside the admin dashboard.
  9. 09Over 360 backend tests covering the API, admin panel, content model, SEO rules and the Odoo contract.

Technical notes

Rendering
Nuxt SSR; Laravel serves JSON only, never HTML
Personal data
None kept for new applications — only a hashed email and send status
URL mapping
Pages resolved by public path in Laravel, so routing has one source