Archived
austin
70af2922f5
The public site was a React SPA. It is now server-rendered Thymeleaf, and the goodie box and catering tables added in the previous commit have a page of their own. The look is unchanged: the templates carry the same Tailwind classes the components did, and every one of the 241 classes the five pages use resolves in the compiled stylesheet. WHAT WENT AWAY. PageMetaController — 148 lines whose only job was to splice per-page <title> and OG tags into one shell with regular expressions, with a test that read the real index.html so that reformatting it failed the build instead of silently breaking the rewriting. A page rendered on the server writes its own head. Also react-router (no client-side routes left), motion, vite-plugin-svgr, and the SPA fallback (platform.web.spa.enabled=false): with the site server-rendered, forwarding a mistyped URL to /index.html would answer with a blank admin shell and a 200 instead of the site's own 404 page. WHAT GOT BETTER ON THE WAY, none of it visible. The category filter is a ?category= link, so every filtered view is a URL you can send someone and a crawler can reach all forty items instead of the twelve the default filter showed. The contact form is a form post: the enquiry is recorded before delivery is attempted, and a refused relay re-renders the page with what the visitor typed still in the boxes. The mobile menu is a <details> — the React version needed four effects to close on navigation, close on Escape, stop the page behind it scrolling, and unmount (a panel parked off-screen still extends the scrollable area, which is how you used to be able to scroll sideways and find the menu); a new document cannot inherit an open menu. THE PUBLIC SITE SHIPS 5 KB OF JAVASCRIPT, and works without it. The product cards are scroll-snap strips, so the photos swipe on a phone and scroll with a trackpad unaided; gallery.js adds the arrows and the dots, and creates them itself rather than having the template render controls that would sit there dead. Tailwind still needs its compiler, so npm remains a BUILD tool: the CLI compiles the templates into static/css/site.css at process-classes (so `spring-boot:run` gets it too), and frontend/ now builds only that stylesheet and the admin. The brand tokens are one file both stylesheets import — the alternative was the shop front and the screen that edits it drifting a shade apart. The stylesheet URL carries ?v=<sha>, because one hand-written CSS file has no content hash and a deploy has to be able to tell a browser that what it cached is stale. The admin is still React and is untouched, apart from losing the router it no longer needs. It is an editor, not content. PlatformContractTest stopped inheriting platform-starter-test's contract and restates it. The shared version asserts that an unknown path forwards to the SPA shell, which is no longer true here, and its test methods are package-private so it cannot be overridden. The platform should decide that assertion from platform.web.spa.enabled — noted in the file. 9 new tests (46 total): every page's real title and og:url, the catalogue and the catering tables in the HTML rather than fetched afterwards, server-side filtering, the 404, and that a crafted ?about= link cannot put words of its own choosing in front of a customer.
67 lines
3.5 KiB
HTML
67 lines
3.5 KiB
HTML
<!DOCTYPE html>
|
|
<html lang="en" xmlns:th="http://www.thymeleaf.org" th:replace="~{fragments/page :: page(${title}, ${description}, ${path}, ~{::content})}">
|
|
<body>
|
|
<div th:fragment="content" class="min-h-screen bg-bakery-50">
|
|
|
|
<header class="container mx-auto px-4 pt-14 pb-10 md:pt-20 md:pb-12 text-center">
|
|
<h1 class="font-adbhashitha text-4xl md:text-5xl text-bakery-900">Contact us</h1>
|
|
</header>
|
|
|
|
<div class="container mx-auto px-4 pb-16 md:pb-24">
|
|
<div class="max-w-2xl mx-auto bg-white p-8 md:p-10 rounded-3xl shadow-xs">
|
|
<h2 class="font-adbhashitha text-2xl md:text-3xl text-bakery-900 mb-2">Get in touch</h2>
|
|
<p class="text-bakery-700 mb-8">
|
|
Or call us: <a href="tel:+13097010660" class="underline underline-offset-4 hover:text-bakery-600">(309) 701-0660</a>
|
|
</p>
|
|
|
|
<!--/*
|
|
A plain form post. The enquiry is validated, written down and mailed by the server, which then
|
|
renders this page again with the outcome — no fetch, no JSON, and nothing to go wrong between
|
|
pressing the button and the enquiry being recorded.
|
|
|
|
Spring Security's CSRF token is added to any th:action form automatically, which is what keeps
|
|
this working on a deployment that has an identity provider configured (there, an unaccompanied
|
|
POST is rejected).
|
|
*/-->
|
|
<!--/* th:unless, not th:if="${!sent}": the attribute is absent on a GET, and SpEL cannot negate
|
|
a null. */-->
|
|
<form th:action="@{/contact}" method="post" th:unless="${sent}">
|
|
<div class="mb-4">
|
|
<label class="block text-sm font-medium text-bakery-800 mb-2" for="name">Name</label>
|
|
<input type="text" id="name" name="name" th:value="${name}" required
|
|
class="w-full px-4 py-2.5 bg-bakery-50 border border-bakery-200 rounded-xl focus:outline-none focus:ring-2 focus:ring-bakery-500 focus:border-bakery-500">
|
|
</div>
|
|
<div class="mb-4">
|
|
<label class="block text-sm font-medium text-bakery-800 mb-2" for="email">Email</label>
|
|
<input type="email" id="email" name="email" th:value="${email}" required
|
|
class="w-full px-4 py-2.5 bg-bakery-50 border border-bakery-200 rounded-xl focus:outline-none focus:ring-2 focus:ring-bakery-500 focus:border-bakery-500">
|
|
</div>
|
|
<div class="mb-4">
|
|
<label class="block text-sm font-medium text-bakery-800 mb-2" for="message">Message</label>
|
|
<textarea id="message" name="message" rows="5" required th:text="${message}"
|
|
class="w-full px-4 py-2.5 bg-bakery-50 border border-bakery-200 rounded-xl focus:outline-none focus:ring-2 focus:ring-bakery-500 focus:border-bakery-500"></textarea>
|
|
</div>
|
|
<div class="flex flex-col items-center gap-4">
|
|
<button type="submit"
|
|
class="px-8 py-3 bg-bakery-600 text-white rounded-full tracking-wide hover:bg-bakery-700 transition-colors">
|
|
Send message
|
|
</button>
|
|
|
|
<!--/* Never claim a success we did not get: say what happened and give them the phone number. */-->
|
|
<p th:if="${error}" role="alert" class="text-center text-red-700">
|
|
<span th:text="${error}">Could not send the message.</span>
|
|
Please call us on
|
|
<a href="tel:+13097010660" class="underline underline-offset-4">(309) 701-0660</a>.
|
|
</p>
|
|
</div>
|
|
</form>
|
|
|
|
<p th:if="${sent}" role="status" class="text-bakery-700">
|
|
Thanks. Your message is on its way, and we will get back to you.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|