jekyll-feed VS lighthouse

XML feeds are often generated by templating, rather than actual XML serialisation. The official Jekyll Feed plugin has this: https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll...

JSON is much more easily generated by a valid generator, and less likely to face serialisation issues.

Awesome. I was able to get this going easily enough on my jekyll-created site that uses the jekyll-feeds plugin. You just have to name the template right and it just works.

https://github.com/jekyll/jekyll-feed/#custom-styling

Disable Jekyll-feed plugin from _config.yml

It looks like this [1] plugin [2] is supported in jekyll / GitHub pages [3].

So, it seems like adding RSS / Atom feeds on a jekyll or GitHub pages site is pretty straightforward.

1. https://github.com/jekyll/jekyll-feed

2. https://docs.github.com/en/pages/setting-up-a-github-pages-s...

3. https://pages.github.com/versions/

Nice site! Another fellow note-taker inspired by Gilles Castel I see ;) Would you be willing to add an RSS feed to your site so people can follow it and get updates? It's been a while since I used jekyll but I think you just need to add jekyll-feed to the Gemfile and config.yml. See here

There is again an easy way out with the jekyll-feed plugin. Add the plugin, do a bundle install and the feed should start appearing at /feed.xml.

I was afraid of that. I was starting to think that how my Atom feed is created is not properly formed XML. I'm using this to build the feed, https://github.com/jekyll/jekyll-feed/blob/master/lib/jekyll-feed/feed.xml. See line number 66 for the content I'm talking about ({{ post.content | strip | xml_escape }}). Maybe I just can't do what I'm trying to accomplish using only XSLT. I just wanted to have the option for the user of having the summary or the full on content with HTML markup and all. BTW, the file I referenced is written with Liquid Template Language.

I have tried using the provided theme like Minima but, I just don’t like it after all. That’s why I think it’s better to create my own. I tried to create the simplest design as long as it is easy to be read. I used Coolors, Google Font, Rogue, Jekyll Paginate, Jekyll Feed, and write a bit of Ruby, CSS, and JS for creating the theme itself. I didn’t think creating this simple blog costs me 2 Saturdays, even though it only consists of as many as 3 pages.

Google Core Vitals now represent the most important metrics to focus on when it comes to technical SEO. Google Core Vitals are a set of standardized metrics that Google uses to evaluate the user experience offered by a web page and assign it a technical SEO grade. Several tools exist to measure and report technical SEO performance, but the most reliable is Google Lighthouse.

- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,

There has been discussion about adding a visual indicator to make the mode more obvious, but it has not made it into Chrome devtools!

I haven't tried it, but you might be able to control throttling by using lighthouse to get performance data: https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md

When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.

You can run a Lighthouse audit in two ways: either on the command line or in a browser. If you want to run audits on the command line, you will first need to install the Lighthouse command:

i wanted to run the lighthouse(lh) docker container on multiple EC2 instances in different regions. I'm thinking of triggering the EC2 instance with the lambda function once the lh container has audited the URL the results will be sent "SUB rest API" which will further update the UI

There's a link to what they mean by mobile network there (https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md) and it says:

Here's the non-psuedo code equivalent that can leverage CompressionStream rather than using a browserified-gzip-library: https://github.com/GoogleChrome/lighthouse/blob/437eb4d757c5...

We use it in Lighthouse for the exact same purpose, a URL #hash full of state. We found that modern browsers support 10mb of data in the hash. https://github.com/GoogleChrome/lighthouse/pull/12509#discus...

Lighthouse: This is an open-source tool developed by Google that allows you to audit the performance of your website. You can use Lighthouse to get a detailed report on your website's Core Web Vitals, as well as other performance metrics. You can run Lighthouse in Chrome DevTools or as a command-line tool.