Skip to main content

2 posts tagged with "Trouble-shooting"

Posts having to do with solving problems

View All Tags

Another Catch-Up Post

· 8 min read
Iain Davis
Iain Davis
Software Engineer, Principal @ IainDavis.dev
TL;DR

There have been a lot of uncommunicated changes in my codebases.

  • I've split off a separate component library called [Docodylus][github-docodylus]
  • I've built a custom internationalization layer for Docodylus on top of Polyglot
  • refactored it into a monorepo (a couple times, actually), and am now preparing to release it into the wild as an open-source project on NPM (just as soon as get the quality-check-and-release pipeline in place)

It's been a long while. I haven't been posting, and virtually nothing has changed here at IainDavis.dev. But I haven't been idle either. Since I last was regularly updating, I made several decisions that have taken a good long while to carry out, and I abandoned some structure and communication while I was doing it. In retrospect, it was maybe unwise, but at the time it felt like quite enough to be dealing with all the things I was dealing with and also be doing the learning I needed to do to implement the changes I wanted.

Fixing Blog-Post Truncation

· 3 min read
Iain Davis
Iain Davis
Software Engineer, Principal @ IainDavis.dev

It's a best-practice in Docusaurus to include a truncation marker in your blog posts. That way, when you're looking at a list of posts, you just see a brief introduction from each post, instead of the full content of the first post pushing the second post clear off the page.

It's where all those "Read more" links are coming from on the main page for my blog.

The default truncation marker for markdown files looks like this:

<!-- truncate -->