If you don’t know which static site generator to use, choose one built in a language that you’re familiar with or want to learn. Under the hood they all use similiar constructs.

The sentiment that you cannot/don’t need to support all browsers is kinda accurate. In many scenarios you’ll never be able to support all browsers due to “business” constraints. Cross browser support is possible though.

But… let’s suppose that the only browser in “real” mainstream use is Chrome. It’s logical then to conclude that the only browser you need to develop for is Chrome, and that deduction works well for many companies.

Firefox’s developer tools excel at finding and fixing accessibility problems quickly. For example, to find all contrast issues on a page fire up the accessibility inspector and scan the DOM tree. My favorite developer tools? You guessed it — Firefox.

The CSS flexible box layout (flexbox) is a great spec. The flex-direction property allows rearranging the position of children inside a flex container. This works in pretty much every browser — even defunct ones like Internet Explorer. Don’t work hard and write JavaScript, be lazy and write CSS.

It’s nice to read an article with real content from real people on the Internet, not SEO spam. These individuals work around the data to page building limitation in hugo by using resources.FromString to programmatically create Markdown. Thought about this, searched to see if it was tried, and it sure was.

Ultimately means that if I get around to it, articles from RSS feeds can be made to appear as native posts in this timeline.

Whenever I’m handcrafting CSS, content selection rules are usually the first declarations on my sheet. Might as well ensure user selected text is readable. Easiest win for accessibility.

::selection {
  color: #fff;
  background-color: #000;
}

::-webkit-selection {
  color: #fff;
  background-color: #000;
}

::-moz-selection {
  color: #fff;
  background-color: #000;
}