Alpe

A marketplace front end is not a brochure: the same markup has to hold a commodity picker with a long taxonomy, an offer list that sorts, a bid table that changes as data arrives, and forms for buyers, sellers and agents who each see something different. It also has to be picked up by another developer and driven from a Laravel application — so guessing at structure, or leaning on a page builder, moves the work rather than doing it.

I built every screen from the design in plain HTML, CSS and JavaScript — no builder, no theme bent into shape — and used the libraries the interface genuinely calls for rather than a bundle: searchable selects for the commodity pickers, sortable tables for the offer lists, date pickers for delivery windows. The agency’s developer took that and wired it into their Laravel application.

• Eight commodity categories, faceted search and a requirement-posting flow
• Offer listings with tonnage, seller and release date, built to be driven from data
• Account, registration and trade-assurance screens for buyers, sellers and agents
• Conventional, readable markup, because someone else had to template it

The front end is mine; the Laravel application behind it is the agency’s. That split is the reason the markup stays plain — the developer templating it should not have to learn my abstractions first:

• HTML5
• CSS3
• JavaScript
• Bootstrap
• jQuery
• Select2
• DataTables

The design shipped as a working interface across the marketplace’s screens, and went into the Laravel build without being reworked to fit it. On an agency job split between two developers, that is the part that decides whether the front end saves time or costs it.