Posts on Next Js.
19 posts tagged "Next Js".
I deployed Next.js to cPanel. The three bugs weren't in any tutorial.
A static Next.js deploy breaks in three specific places on cPanel: the LiteSpeed .htaccess configuration, next/image's optimisation API assumption, and a trailing-slash 404. None of the tutorials document them together. Eight chapters now do.
The link preview is blank and the build passed
Sharing a captainrandom.co.uk album page on WhatsApp returned a blank white card. Per-page og:image overrides were working on writing posts; the root layout had no default image. Typecheck passed, build passed, Lighthouse passed — WhatsApp showed a grey rectangle.
The og:image that wasn't there: blank WhatsApp previews and a pre-ship check no CI runs
Sharing a captainrandom.co.uk album link on WhatsApp returned a blank white card. The site had structured data, a navigation spec authored by 16 parallel agents, and data-driven course stubs. It had no default og:image. The gap was invisible until a real phone surfaced it.
The in-chapter TOC needed live JavaScript. It still got a mockup first.
The captainrandom learning hub navigation retrofit ran five phases. Every one went through the UI gate — interactive approval mockup before production code. The most interesting case was P4: the subsystem's only client-side component, with a live IntersectionObserver scroll-spy in its mockup, still approved before a line of React was written.
The backlog called it a content gap. It was navigation.
Completing an eight-chapter course on the learning hub felt like progress. Then I looked at what had actually moved the needle — track sections, prerequisite chips, and a JSON-LD breadcrumb. The backlog had been mis-filing the bottleneck for months.