MandarisWe've started a new project which requires heavy, creative theming, so I made a prototype to test some ideas out.
I really like this article as it breaks down the reasoning of why they are doing what they are doing. It has some examples that you can follow along with and leaves me thinking about how I can take this knowledge into my own development.
Discovered via Andy Bell
This article by Schalk Neethling talks about the access portion of accessibility. It's something that I think about for the base portion of my theme and I hope that you'll read it and spread the message.
This is the first interview in Technical Writing Chats, a series where I speak with technical writers about their day-to-day role and how they got started in their career. Today's interview is with Ally Sassman, a Senior Technical Writer at New Relic. I sincerely hope you enjoy!
This is the first post in James' series.
I'm hoping to pick up a couple tips throughout the series to improve the writing that I do on my blog.
This got me thinking: how are curly braces used in English today? Many English keyboards, such as the Macbook Air keyboard on which I am typing this blog post, have curly braces as a character you can type with the shift key pressed. If curly braces are on our keyboards, they would have to either have some use in language, or sufficient use as a punctuation in computational contexts?
I can't recall ever seeing these outside of the context of programming.
I keep getting older, and the text size on Daring Fireball keeps staying the same.
I feel this soo much. It's part of the reason that I make the default font as big as it is. I understand that a user might have a default style sheet or setting. I feel that designing for a larger initial font, makes this particular theme more flexible.
Earlier this week, with a spark for building but no particular idea in mind, I started to think about the Linux manual page. Could I serve my blog posts as Linux manual pages? Herein lay an adventure.
WHOA! This completely blew my mind!
This study compares two websites with identical design: the commercial Spotlight template from developers of Tailwind vs the same site with semantic CSS
I found this via Robb Knight's mastodon/website and laughed to myself when I read No Comment
.
I've been using tools that help developer things faster
for years. It feels like all the time we save accrues interest and we have to payback in other costs.
As you can imagine, we spend a lot of our time working on really, really old books. So why not create a website out of really, really old technology?
A pretty interesting read. It's part of what got me interested in static website generation. Also, came across the word "paean" which I haven't seen in so long that I thought it was a typo.
