It's been a while since I posted here!
Actually, I posted here about a week ago about some of the things I was working on with Nova, but I wrote it in a bit of a rush, and I hated that blog post. It was disorganized and the content didn't really relate to the title at all, so I deleted it.
Since then, this week and a goodly chunk of last week have been all about producing content for this here website.
Today, we took a major step toward automating the deployment of this site, eliminating manual steps and reducing the risk of errors.
Now, every pull request (PR) generates a preview build, and every merge to the
main branch automatically triggers a production deployment. This new setup
speeds up the process, ensures consistency, and minimizes the chances of
mistakes.
Today, we focused on streamlining our automated preview deployment process for PRs, ensuring that each pull request includes a live preview of the Docusaurus site, Storybook components, and test reports.
The main goal was to automate the deployment of a fully functional preview for every PR, complete with Docusaurus builds, Storybook, and test results. This meant dealing with dynamic URLs, managing build artifacts, and ensuring everything worked in harmony.
Automating the preview process means changes to the site are instantly available for review, speeding up development and reducing the chance of bugs. This allows us to deliver updates faster while keeping quality high.
It's been a few days since I posted. That's not because I haven't been busy, it's because setting up unit testing turned out to be much harder than I anticipated.
To be fair, I was trying to achieve a somewhat complex setup.
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 -->
This post is just a listing of some of the things I'm planning to add here in the coming days.
One of the first things my outplacement coach told me was that I ought to be posting to LinkedIn regularly. I knew I wanted to have updates specific to this website here on my blog, and I figured I'd just have to cross-post them manually.
It turns out that's not so!
In my last blog post, I used a diff to show how my SVG files had changed.
For those who don't know a diff is an operation on two files that shows a graphical representation of how one is different than the other.
They look like this:
| on the command line | in a nice UI like GitHub |
|---|---|
 |  |
After creating my logo, I wanted to turn it into a re-usable React component that would respond to theming, and let the logo variant be controllable by properties, so that essentially, I would only need one component that I could use wherever I wanted a logo
| expanded | compact | compactSquare |
|---|---|---|