briggysmalls / blog Goto Github PK

It doesn't just display in the browser tab title, but is also used by RSS readers / aggregators, shortcuts, bookmarks etc

In my quest to find the rss feed I tried a couple of common URLs (/feed, /rss.xml) which got me to a github pages default 404. Consider something more graceful

All the diagrams can be generated as SVGs.

I did try to use them, but something about the CSS styling was making them look rubbish.

But vector graphics will look sharper, so when there's time to root out the issue this would be a better approach.

A post about using AWS IoT SDK on a raspberry pi

Apparently this isn't cool anymore.

Instead I should just have an indicator that the page is external, and allow my users to make the call themselves. #UX bro.

I want to keep my posts snappy (~500 words). I'm not exactly sure why, just do.

So I will end up with a lot of posts grouped as a 'series'.

This is different from what tags ought to be, e.g. go or aws, rather than a series like detectordag or flipdot.

A taxonomy list page should really list in order that the taxonomy weight has been given, rather than 'most recent' first

Horizontal scrolling on error messages is a pain. There should be some nice way to wrap text whilst still making it obvious when things are a one-liner.

You are a nerd who builds his CV on GitLab with LaTeX.

The world must know.

Issue #19 came about because the RSS feed is not very 'discoverable'.

A link to the feed should be added to the /posts page.

There isn't currently a good way to navigate through a series.

Really, I think the behaviour I want is for next/prev to work based on URL slug, but .NextInSection doesn't really do what I wanted. A section is only the top-level directory under content.

When I build my CV I run a spell-checker.

Obviously adding tech words to a custom library is annoying, but it also saves me from looking like an idiot.

The same might be worth doing here.

For some reason the theme makes the homepage a stupid height: greater than that of the screen size.

It really annoys me, as most of the time the content doesn't need that space, and it makes the centring off centre!

Playing with mlflow was really annoying when I was trying to run using sude (yes, yes, I know that is terrifying)

https://www.petefreitag.com/item/877.cfm

Go projects tend to use makefiles for running 'tasks'.

But make's strengths are in tracking the inputs and outputs of build steps in order to optimise a complicated build process. Not executing one-off commands (e.g. linting).

I'd like to find some alternative. mage could be it?

Currently the only way to end up on a series page is to land on a single blog post and then navigate back using the intro prompt.

There should probably be a way to get there from the posts page.

I've found myself mentioning balena Pi docker builds in the detector-dag project, and the pain.

I should have a post I can refer to that discusses this when I document the flipdot project!

Particularly if you are reading a series, it would be nice if the next post in a series was suggested.

Add something like pa11y for testing accessibility.

A cursory google doesn't return much, but I'd really like to have a formatter force all my markdown to be a sensible line width.

Probably the biggest project so far. Worth having written up.

Don't forget to add:
rel="noopener noreferrer"

https://developers.google.com/web/tools/lighthouse/audits/noopener

Bonus points if it is kept locally on your server

https://www.producthunt.com/alternatives/google-fonts

https://alternativeto.net/software/google-web-fonts/

Currently the build pipeline fails, 'nuff said.

I struggled with deploying a directory _gen because it was prefixed with an underscore.

Turns out I needed to add .nojekyll so that github pages would deploy it.

Then on top of that gh-pages needed to be given the --dotfiles argument.

It would be good to make a post about that

Support those of us still using this old protocol

The tracking code doesn't seem to have been enough to turn on analytics.

Perhaps the HUGO_ENV setting in the build pipeline hasn't worked correctly?