rs2009/ruds.io
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: rss and wording

Browse source
This commit is contained in:
Rudra Saraswat 2026-04-07 15:59:15 +01:00
parent 73dc84b479
commit 997e30c609
2 changed files with 11 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

12
src/pages/posts/blendOS-v5-distro-switching.mdx
View file

@ -1,8 +1,8 @@
---
layout: '../../layouts/PostLayout.astro'
title: 'devlog: distro-switching & OCI system images in blendOS + a personal update'
title: 'devlog: distro-switching & OCI system images in blendOS, collaboration with Framework, and a personal update'
pubDate: 2026-04-05
description: 'An account of how I implemented the ability to switch between distributions on blendOS and a collaboration with Framework, plus a personal update at the end.'
description: 'An account of how I implemented the ability to switch between distributions on blendOS and news of a collaboration with Framework, plus a personal update at the end.'
author: 'ruds'
tags: ['general']
---
@ -21,7 +21,7 @@ All of that, driven alone by the change of a single line (maybe two) in a simple
<br /><hr /><br />
As you may have well figured, blendOS v5 will include support for a variety of different distributions via a new extensible tracks system. At the time of writing, there have been implemented GNOME, Plasma, and headless tracks for Arch-based and Ubuntu-based blendOS systems each, switching between which entails changing a single line within one's `/system.yaml` file; and we have every intention of introducing support for several other distributions.
As you may have well figured, blendOS v5 will include support for a variety of different distributions via a new extensible tracks system. At the time of writing, there have been implemented GNOME, Plasma, and headless tracks for Arch-based and Ubuntu-based blendOS systems each, switching between which entails changing a single line within one's `/system.yaml` file; and I have every intention of introducing support for several other distributions.
```yaml
# arch | ubuntu
@ -32,7 +32,7 @@ track: "https://git.blendos.co/blendOS/tracks/-/raw/v5/arch/gnome.yaml"
```
↑ *`/system.yaml` file*
Additionally, as part of our snazzy new `/system.yaml` configuration format, one may implement support for their own distributions of choice, building upon OCI images. For example, displayed underneath is the configuration for Ubuntu, based atop a custom Ubuntu container image (to reduce update times, though one could also use the pre-existing `ubuntu:latest` image from DockerHub for such a configuration):
Additionally, as part of our snazzy new `/system.yaml` configuration format, one may implement support for their own distributions of choice, building upon OCI images. For instance, illustrated underneath is the configuration for Ubuntu, based atop a custom Ubuntu container image (to reduce update times, though one could also use the pre-existing `ubuntu:latest` image from DockerHub for such a configuration):
<iframe frameborder="0" scrolling="yes" style="width: 100%; height: 556px;" allow="clipboard-write" src="https://emgithub.com/iframe.html?target=https%3A%2F%2Fgithub.com%2Fblend-os%2Ftracks%2Fblob%2F0e28a76b84bf4b83a4dea78dbadfdb7a74dc5057%2Fubuntu%2Fbase.yaml&style=default&type=code&showBorder=on&showLineNumbers=on&showFileMeta=on&showFullPath=on&showCopy=on&maxHeight=500"></iframe>
@ -44,9 +44,9 @@ However, it is to be noted that despite the majority of core system functionalit
### collaboration with framework
Earlier this year, the team at [Framework](https://frame.work/) had reached out to me about the possibility of introducing official blendOS support for their hardware; speaking as an advocate of repairable hardware, there could not have been obvious choice than to take it on.
Earlier this year, the team at [Framework](https://frame.work/) had reached out to me about the possibility of introducing official blendOS support for their hardware; speaking as an advocate of repairable hardware, there could not have been obvious choice than to take on this collaboration -- in an era marred by disposable electronics and planned obsolescence, the Framework 16 delivers a nonpareil extent of upgradability and extensibility.
I was subsequently sent a Framework 16 last month, enabling me to work towards supporting the laptop as part of blendOS v5, aside from supplying the project with much-needed dedicated hardware for development; indeed, it is the very same laptop as that pictured above. As a newer and lesser-known Linux distribution, we greatly appreciate the support from Framework.
I was subsequently supplied an HX 300-series Framework 16 last month, enabling me to work towards supporting the laptop as part of blendOS v5, aside from supplying the project with much-needed dedicated hardware for development; indeed, it is the very same laptop as that pictured above. As a new and upcoming Linux distribution, we greatly appreciate the support from Framework.
<br /><hr /><br />

9
src/pages/rss.xml.js
View file

@ -1,11 +1,12 @@
import rss, { pagesGlobToRssItems } from '@astrojs/rss';
import rss, { pagesGlobToRssItems } from "@astrojs/rss";
export async function GET(context) {
return rss({
title: 'ruds | blog',
description: 'The incoherent ramblings of an emo madman with a technological inclination.',
title: "ruds | blog",
description:
"The incoherent ramblings of an emo madman with a technological inclination.",
site: context.site,
items: await pagesGlobToRssItems(import.meta.glob('./posts/*.md')),
items: await pagesGlobToRssItems(import.meta.glob("./posts/*.{md,mdx}")),
customData: `<language>en-us</language>`,
});
}