Chris Burnell · Replies

Reply to Jeremy Keith

2026-01-08T11:53:10-04:00

Thanks, Jeremy, I appreciate it!

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to What's Your Style?

2024-08-16T16:13:34+08:00

If I go back and look at the first version of my website from 2008, it looks like I was a style.css guy.

I resent so much about that decision. 😂

I mean, I guess they are called Cascading Style Sheets, not Cascading Styles Sheets, so maybe there’s an argument to be made there for using style.css, but I won’t be the one defending that position!

Recently, though, I tend not to use either style.css or styles.css.

Ever since the notion of Critical CSS entered the scene, I’ve named things a bit differently. Because the idea here is to split a website’s styles into two sets—one that is required for above the fold content, or many/all pages; and another that is needed to style the rest of the website—I’ve started naming the two stylesheets critical.css and defer.css.

What actually happens on my website these days is that I use the 11ty plugin, eleventy-plugin-bundle, to combine various SCSS partials into two buckets (also named critical and defer), and the plugin generates a chunk of CSS that gets inlined in the <head> and another chunk that gets spat out into a content-hashed file location and gets referenced by a <link> tag.

So, in short, I’ve still got a fondness in my heart for ol’ faithful, /css/styles.css, but what I actually do in practice differs. That being said, I think there’s a future where, like native Web Components for example, CSS comes bundled with the HTML that it’s associated with as a best practice. And with that being a possibility, I think it’s reasonable to assume that I’ll be naming my CSS files styles.css once again!

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to Joining CSSWG

2023-07-21T10:56:30+01:00

What great news! There’s no doubt in my mind that you’ll not just be useful, but will make a really positive and deeply-appreciated impact on the web. Congratulations!

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to eleventy-cache-webmentions

2022-09-13T12:23:33+01:00

Happy to announce that I’ve released version 1.0.0 of Eleventy Cache Webmentions! Although it introduces some breaking changes for earlier versions, 1.0.0 makes it a lot easier to attach Webmentions to your pages as data using eleventyComputed. Check out my recent post, Webmention Setup for Eleventy, to get started!

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to eleventy-cache-webmentions

2022-06-14T16:18:09+01:00

Just updated eleventy-cache-webmentions to version 0.2.0, a shallow first attempt at making the package work with any Webmention server, not just Webmention.io.

Given a couple of assumptions about how the data is returned from the server, this change allows you to use different Webmention servers, hopefully lessening the inherent dependency on Webmention.io.

This change does mean that there are now two more required fields that need to be passed to the plugin when invoking it in your .eleventy.js file with addPlugin():

const pluginWebmentions = require("@chrisburnell/eleventy-cache-webmentions")
module.exports = function(eleventyConfig) {

eleventyConfig.addPlugin(pluginWebmentions, {

// these 3 fields are all required!

domain: "https://example.com",

feed: "https://webmention.io/api/mentions.jf2?domain=example.com&amp;token=${process.env.WEBMENTION_IO_TOKEN}&amp;per-page=9001",

key: "children"

})

}

The above example, which I’m hoping is simple to update in existing configs, outlines how to use the plugin with Webmention.io.

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to a previous Note

2022-05-15T18:00:00+01:00

Happy to say the sparklines are going well—pushed an update yesterday, in fact, to allow them to inherit the color of wherever they are in the DOM for the colour of the line itself.

Still working on posting a bit more! 😅

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to eleventy-cache-webmentions

2022-01-15T21:15:44+00:00

Fixed a bug in eleventy-cache-webmentions from a silly assumption I made about determining a since value to get new Webmentions when the cache exists.

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to a previous Note

2021-11-29T15:53:57+00:00

Update: still not caught my own tail—I'll get back to that when I find my way out of these rabbit holes, and on that note, I bumped up to 1.708 commits/day as of today.

Continue to do with that information what you will.

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to JavaScript30 Day #02 - Wes Bos’ JavaScript30 course, grouping operator, HOCs in ReactJS.

2020-10-07T16:40:31+01:00

Uh oh, I’ve been found out… Ru totally sniped me with her call-out, in the best way possible!

I guess I better double-down and make this a proper thing for myself—30 days, 30 JS challenges—let’s do this!

I made a little Eleventy site as a front end for my progress, too.

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Reply to a previous Note

2020-08-06T17:06:00+01:00

Eleventy is a go! Managed to migrate all of my content, pages, and a whole lot more. Article about the transition coming soon!

Thanks for subscribing and reading this post via RSS!

You can read this post and others on my website.

Chris Burnell · Replies

Reply to Jeremy Keith

Reply to What's Your Style?

Reply to Joining CSSWG

Reply to eleventy-cache-webmentions

Reply to eleventy-cache-webmentions

Reply to a previous Note

Reply to eleventy-cache-webmentions

Reply to a previous Note

Reply to JavaScript30 Day #02 - Wes Bos’ JavaScript30 course, group­ing op­er­a­tor, HOCs in ReactJS.

Reply to a previous Note

Reply to JavaScript30 Day #02 - Wes Bos’ JavaScript30 course, grouping operator, HOCs in ReactJS.