Posts on Learning.
11 posts tagged "Learning".
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.
Eight chapters, two Workflows: which parts of a course parallelise
Shipping the static-next-cpanel course via two ultracode Workflows revealed a clean partition: chapter bodies fan out to parallel agents without coordination cost; prerequisite ordering and the curriculum through-line do not.
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.
The cheapest phase in a seven-phase plan was also the highest-leverage one
Prerequisite chips in the learning hub — three words, one arrow, no JavaScript — outperformed every other navigation phase by the only metric that matters at the chapter level: whether a reader knows what to read first. The evidence is what the other six phases cost by comparison.
The read-first chip outperformed the TOC, track sections, and site-wide search
The learning hub navigation programme ran six phases across two days: track sections, a scroll-spy TOC, prerequisite chips, and site-wide Pagefind search. The smallest phase shipped fifth and delivered more navigability than all the rest combined. The structural reason was there in the spec before the build started.