It only took a few hours tonight to set up a new VPS machine with Docker, LetsEncrypt, and Drone.io to be able to build and deploy my Hugo blog to a test site. The whole CI/CD pipeline takes less than ten seconds to finish.
I will have to write up all of the details, including my docker-compose files, nginx configs, and .drone.yml later on this week. It's all super exciting to see it come together.
The official Angular documentation discussing Reactive Forms shows how one can use groups and arrays to organize a form, and to dynamically add to it. The drawback of the example on that page is that everything is in a single component.
Once a component starts to grow in size and complexity, it becomes desirable to decompose it into multiple smaller components. At this point, there are a number of ways to break up the form into a set of nested form elements.With many thanks to Using Web Mentions in a static site (Hugo), published by Paul Kinlan in October 2019, I have added Webmention support to the site.
For now, I am using Webmention.io to handle the heavy lifting of providing the Webmention end-point, the same way the above-referenced article describes.
With only minor modifications to the Node.js script from the article, I can pull down all mentions for my domain from Webmention.My Semantic IndieWeb Theme currently being used for the site has been updated to provide a more responsive design. On landscape tablet or wider screens, the author card now displays in a column on the right side of the screen. On smaller devices, such as ones phone, the author card will continue to render at the end of the page.
There is a fair amount of yet-to-be-used whitespace under the author card in the wide screen view.While waiting at the local Panera Bread shop for my lunch order, I noticed a fellow patron who was wearing a Miskatonic Observatory t-shirt. It made my day.Today I realized that I had incorrectly set up a permalinks definition for the posts section of the website in a way that left the posts/ folder out of the generated path name. That wasn't how I intended the site to be laid out on-disk.
Since my content organization was the way I wanted things to end up, the permalinks definition was redundant as well as incorrect. However, I realized that I couldn't just remove it, as any-and-all links that I had previously shared on Mastodon would be broken!
Inspired by the many blog sites out there that display a series of icons
linking to the site author's other sites and social media profiles, I
set out to add the same to my site.
Apparently, LinkedIn doesn't actually support With the update of the site to use my new (work-in-progress) theme with IndieWeb support, I have now completed both Level 1 checkpoints from IndieWebify Me:
Get your own domain name Set up Web Sign In I can successfully authenticate using my website URL on IndieAuth.
Soon to come: adding h-card and h-entry microformat markups to better integrate wtih other IndieWeb sites.Site has been update to use my new work-in-progress Semantic IndieWeb theme. This brings configurable rel="me" tags as <link>...</link> blocks in the <head>...</head> of each page, enabling IndieWeb authentication.
rel="me" links back to ones
personal website(s). How very disappointing.