Smart Connect — Malta
2026
Smart Connect
Teal sea and Mediterranean orange, with the utility framework compiled out of the page rather than shipped into it.
Delivered to
Malta — sales recruitment
Smart Connect careers
Styling
Tailwind compiled to a static file
Build: Vite, for the stylesheet only
Techniques
2
2 constants, formulas and guards
A recruitment site for sales careers in Malta, built around the one thing a candidate actually wants to know — what the progression looks like. Open roles are accordions, and applying opens a form with the role already filled in, so nobody has to retype which job they are looking at. Its most useful decision is one a visitor never sees: the utility CSS framework it was prototyped with does not ship.
Offline
A sales-career recruitment site. Shipped with its forms deliberately unwired — that is stated on this page rather than left for a reader to discover. Claims are made against the source.
The CSS framework was a prototyping tool, and it does not ship.
What was built, and for whom.
Smart Connect careers
Malta — sales recruitment
en
Role accordions with a pre-filled application modal, and a compiled stylesheet replacing a runtime CSS compiler.
Each one starts with something that was broken.
- 01
The framework was a prototyping tool, not a shipping one
The failure
The CDN build of a utility CSS framework is wonderful for building fast and terrible to ship: it sends a compiler to every visitor, which then generates the stylesheet on their device, after render has already started. The page is styled late, on hardware you do not control.
The decision
Keep the authoring experience and delete the runtime — compile the utilities actually used into a static stylesheet at build, and ship that. The markup is unchanged; the browser simply receives a stylesheet instead of the machine that writes one.
- constantREADME.md / css/tailwind.css
“Compiled Tailwind utilities + preflight (static — replaces the old Play CDN)”
- 02
Apply already knows which job you meant
The failure
A shared application form asks the candidate to re-select the role they just clicked. It is a small tax, and it is charged at the exact moment the page has finally persuaded them — which is the worst possible moment to introduce friction.
The decision
Open the form from the role and carry the role into it, so the modal arrives pre-filled. One form serves every position and the candidate never restates something the page already knows.
- constantjs/main.js
Apply-button → application modal, role pre-filled from the accordion it was opened from
Every animation, with what it does when asked for less.
The last column is the one worth reading. “Respects reduced motion” is easy to assert and easy to skip, so where it is not true here, it says so.
Section reveals
On intersection, once
Ease-out
Guarded by observer support; the settled state is the default.
Stats band
On intersection
Ease-out
Observer-gated.
Modal
Short fade and lift
Ease-out
Unaffected — it is a state change.
What it was built on, what is claimed, and what is not.
Styling
Tailwind compiled to a static file
Replacing the CDN build, which ships a compiler to the browser. See the technique.
Build
Vite, for the stylesheet only
There is no application to bundle. The build step exists to turn utilities into a file.
Behaviour
Vanilla JS
Reveals, a stats band, accordions and the modal. Nothing that needs a framework.
Claimed — and how to check it
The stylesheet is compiled, not generated in the browser
The static compiled stylesheet in css/, and the README's note on replacing the CDN build.
Applying pre-fills the role
The apply handler in js/main.js.
Not claimed
- The forms do not submit. They confirm on the client and no backend was attached — the repository says so, and so does this page.
- No application, hire or traffic figure.
- No performance measurement. The framework change is an architectural claim, not a measured one.
Read from the repository's scripts and its stated build setup.