Metalsmith VS web.dev

Metalsmith — the best customizable SSG

I use Metalsmith. Been happy with it. I build my site into a self-contained nginx docker image.

const Metalsmith = require('metalsmith') const markdown = require('@metalsmith/markdown') const layouts = require('metalsmith-layouts') const permalinks = require('@metalsmith/permalinks') const collections = require('metalsmith-collections') Metalsmith(__dirname) .metadata({ sitename: 'Website Name', description: "Website description.", generator: 'Metalsmith', url: 'https://metalsmith.io/' }) .source('./src') .destination('./build') // .clean(true) .use( collections({ projects: 'pages/*.md', reverse: true, refer: true }) ) .use(markdown()) .use(permalinks()) .use( layouts({ engineOptions: { helpers: { formattedDate: function (date) { return new Date(date).toLocaleDateString() } } } }) ) .build(function (err, files) { if (err) throw err })

I also started to move to hugo, but they didn't merge the pr [2] which would have helped in the transition. :(

The look is still similar to what it was in the beginning, in terms of colors at least.

[1] https://github.com/metalsmith/metalsmith

Metalsmith

A static site generator I've been enjoying lately (and using for my blog) is Metalsmith: https://metalsmith.io/

It feel like it's the best of both worlds, because it's simple to learn and customize, but there are plugins for the things you don't want to spend time writing yourself.

For example, I'm using plugins to: check for broken links, generate an RSS feed, and run a test server with automatic reloading.

But then I was able to easily add in my own code to handle relative links, generate Graphviz diagrams, and format dates.

One other recommendation: I hated almost every template language I ran across (Hugo's, Liquid, Nunjucks, EJS), but I'm thrilled with the simplicity of Handlebars (https://handlebarsjs.com/), although it is a bit limiting and the "block helper with parameters" syntax is strange (perhaps an indicator that I'm trying to do too much in the templating language!).

I believe Metalsmith [1] is trying that approach

[1] https://metalsmith.io/

Before we start creating pages in our application, it's important to understand how Next.js renders content. The framework supports multiple rendering methods including server-side rendering (SSR), static site rendering (SSG), and client-side rendering (CSR). There are many pros and cons to each rendering method (too many to cover in this post) so if these concepts are new to you, Google’s web.dev site has a very good introduction to rendering on the web that can help you understand rendering options.

The lifecycle of an interaction. Source: web.dev

Probably not, it's the CSS used so far, so if there are elements you've not interacted with, that's an issue. This web.dev article gives some tools you can use https://web.dev/articles/extract-critical-css

I noticed the same for Google's site https://web.dev/

The last article pushed to the feed was "Changes to the web.dev infrastructure" few months ago https://web.dev/blog/webdev-migration

The feed still there but with no updates https://web.dev/feed.xml and on the site you can see new articles published.

Is sad that on a infrastructure revamp of a modern site, the RSS feed was left out of the features list (at least for now).

Upon testing on Firefox and Mi Browser, there was no triggering of the BeforeInstallPrompt event, as expected. However, I noticed that web.dev manages to display a prompt on these browsers, even though they theoretically lack support for the BeforeInstallPrompt event.

web.dev, maintained by Google, including posts by Chrome developers and their co-workers,

In a old web.dev articleI came across the word "Incremental (Re)Hydration" which is linked to a Glimmer.js-Blog post (also called "Incremental Rendering" there) confuses me. Is Incremental (Re)Hydration the same as Progressive (Re)Hydration? Reading the Glimmer-Blog article it seems so, but in the web.devarticle it seems to be something different.

Web.dev newsletter - though it's not a weekly newsletter and it's only content from web.dev (though really high quality content)

Just open up a text edi web developers are self-taught. a website. That's what I did. Some people like this: https://web.dev