Merge main into UM40 changes

.gitignore

@@ -19,3 +19,5 @@ pnpm-debug.log*
 
 # macOS-specific files
 .DS_Store
+
+bun.lockb

src/consts.ts

@@ -37,6 +37,7 @@ export const SIDEBAR: Sidebar = {
       { text: "Getting Ultramarine", link: "en/installation/getting" },
       { text: "Installation", link: "en/installation/installation" },
       { text: "Post-Installation", link: "en/installation/postinstall" },
+      { text: "Advanced Post-install steps", link: "en/installation/post-advanced" }
     ],
     Contributing: [
       { text: "Overview", link: "en/contributing/contributorguide" },
@@ -62,7 +63,10 @@ export const SIDEBAR: Sidebar = {
       { text: "The Shell", link: "en/linux/shell" },
     ],
 
-    Usage: [{ text: "Gaming on Ultramarine", link: "en/usage/gaming" }],
+    Usage: [
+      { text: "Gaming on Ultramarine", link: "en/usage/gaming" },
+      { text: "Localization", link: "en/usage/l10n" },
+    ],
 
     "Release Notes": [{ text: "Errata", link: "en/release/errata" }],
     // Chromebook: [

src/content/docs/en/installation/post-advanced.mdx

@@ -0,0 +1,89 @@
+---
+title: Advanced Post-Installation Steps
+description: Learn how to further configure your Ultramarine Linux installation.
+---
+
+import Alert from "../../../../components/Docs/Alert.astro";
+
+## Use systemd-boot as the bootloader
+
+Ultramarine Linux currently still uses GRUB as the default bootloader for compatibility reasons. However, if you have a UEFI system, you can simply switch to
+systemd-boot, which is a more modern bootloader.
+
+<Alert type="warning">
+  This step is optional. You can skip this step if you don't want to use systemd-boot.
+  Make sure to back up your data and have a live USB ready in case something goes wrong.
+  Incorrectly configuring a new bootloader can make your OS unbootable.
+</Alert>
+
+1. Make sure you turn off Secure Boot in your UEFI settings for now, You can re-enable it later after [Setting up Secure Boot](#set-up-secure-boot)
+2. Remove GRUB from protected packages:
+  ```bash
+  sudo rm /etc/dnf/protected.d/grub*
+  ```
+3. Start uninstalling GRUB:
+  ```bash
+  sudo dnf remove -y grubby grub2\* memtest86\* && sudo rm -rf /boot/grub2 && sudo rm -rf /boot/loader
+  ```
+4. Install unsigned systemd-boot binaries and the `sdubby` tool:
+  ```bash
+  sudo dnf install systemd-boot-unsigned sdubby
+  ```
+5. Install systemd-boot to the ESP:
+  ```bash
+  # Copy your current cmdline options just in case
+  cat /proc/cmdline | cut -d ' ' -f 2- | sudo tee /etc/kernel/cmdline
+  # Install systemd-boot
+  sudo bootctl install
+  # Now, reinstall and regenerate the current kernel entry
+  sudo kernel-install add $(uname -r) /lib/modules/$(uname -r)/vmlinuz
+  # Reinstall the kernel again, just in case we need to trigger some hooks
+  sudo dnf reinstall -y kernel-core
+  ```
+6. Reboot your system and make sure it boots correctly, run `sudo bootctl` to check if the boot process is correct.
+7. (Optional) Proceed to [Set up Secure Boot](#set-up-secure-boot) if you want to re-enable Secure Boot.
+
+
+
+## Set up Secure Boot
+
+[Secure Boot] is a UEFI security protocol that secures the boot process by ensuring that
+only signed executables are allowed to boot. While Ultramarine Linux's bootloader shim is signed by Microsoft and Red Hat,
+you may want to use a different bootloader (i.e systemd-boot or rEFInd) or kernel. In that case, you will need to manually enroll
+and sign the files with your own keys.
+
+Fortunately, there's a tool to automate this called [sbctl]. You can install it from the Terra repository:
+
+<Alert type="info">
+  `sbctl` is only available on Ultramarine/Fedora 40 and later.
+</Alert>
+
+```bash
+sudo dnf install sbctl
+```
+
+After installing `sbctl`, you can use it to enroll, sign, and manage your Secure Boot keys. For example, to generate a new key and enroll it in your UEFI firmware:
+
+```bash
+# Generate a new key
+sudo sbctl create-keys
+# Enroll the key
+sudo sbctl enroll-keys
+```
+
+You can then use `sbctl sign` to sign your kernel, initramfs, and bootloader binaries. For example:
+
+```bash
+# Sign the kernel
+sudo sbctl sign /boot/vmlinuz-$(uname -r)
+```
+
+However, once you have installed sbctl, it should've already set up a hook to sign the kernel, initramfs and bootloader binaries automatically on kernel updates.
+
+After signing the necessary files and enrolling them in your firmware, you can re-enable Secure Boot in your UEFI settings.
+
+
+[Secure Boot]: https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-secure-boot
+[sbctl]: https://github.com/Foxboron/sbctl
+
+#### [← Back To: Post-installation](/en/installation/postinstall)

src/content/docs/en/installation/postinstall.mdx

@@ -42,7 +42,22 @@ Then reboot your system.
 
 ## Install Codecs
 
-Ultramarine Linux includes codecs for most of the media you'll come across. You shouldn't need to install any additional codecs.
+Ultramarine Linux includes codecs for most of the media you'll come across. **You shouldn't need to install any additional codecs.** Most of these packages below should be installed by default, excluding
+the VLC and MPV media players, and the `libdvdcss` library.
+
+However, if you find yourself in the situation where you do not have those codecs, or require additional codecs other than we have provided (i.e obscure formats, or proprietary codecs not included in any repositories), you can look into the following packages:
+- `x264` and `x265` for better H.264 and HEVC video support - Developed by the VideoLAN (VLC) project.
+- [FFmpeg](https://ffmpeg.org/) (`ffmpeg`) - A cross-platform multimedia framework that can manipulate, convert and transcode to and from various media formats.
+- [VLC Media Player](https://www.videolan.org/vlc/) (`vlc`) - A free and open-source media player that can play most multimedia files, can also be used to test out the codecs' functionality.
+- [MPV](https://mpv.io/) (`mpv`) - A free and open-source media player that can also play most multimedia files. Can be used as a lightweight alternative to VLC.
+- [libvpx](https://www.webmproject.org/) (`libvpx`) - A free and open-source codec for VP8 and VP9 video formats.
+- [libdvdcss](https://www.videolan.org/developers/libdvdcss.html) (`libdvdcss`) - A library that can be used to read encrypted DVDs. This is not legal in some countries, so please check your local laws before using it. We also do not provide decryption keys for any encrypted DVDs.
+- [Opus](https://opus-codec.org/) (`opus`) - A free and open-source audio codec that can be used for both speech and music. Should be installed by default.
+- [OpenH264](https://www.openh264.org/) (`openh264`) - A free and open-source codec for H.264 video formats. Should be installed by default, required for WebRTC and partially Firefox.
+- [aptX](https://www.aptx.com/) (`pipewire-codec-aptx`) - A proprietary codec for high-quality audio streaming over Bluetooth. Required for wireless Bluetooth audio devices that support it.
+- `nv-codec-headers` - NVIDIA's codec headers for encoding and decoding video on NVIDIA GPUs. Required for hardware-accelerated video encoding and decoding on NVIDIA GPUs. May not be used by default assuming you do not have an NVIDIA GPU.
+- [LAME](https://lame.sourceforge.io/) (`lame`) - A free and open-source MP3 encoder. Required for encoding MP3 files.
+- `PackageKit-gstreamer-plugin` - PackageKit plugin that helps you install the above codec packages using GNOME Software/KDE Discover.
 
 ## Set up Backups
 
@@ -53,4 +68,6 @@ Instructions are available on the [Pika Backup] and [Déjà Dup] websites.
 [Déjà Dup]: https://wiki.gnome.org/Apps/DejaDup
 [Pika Backup]: https://apps.gnome.org/PikaBackup/
 
+#### [Next Up: Advanced Post-installation steps →](/en/installation/post-advanced)
+
 #### [← Back To: Installation](/en/installation/installation)

src/content/docs/en/release/upgrade-to-ultramarine-40.mdx

@@ -0,0 +1,36 @@
+---
+title: Upgrade to Ultramarine 40
+description: "A temporary notice for the 39 to 40 upgrade path."
+---
+
+This page is a temporary notice for upgrading Ultramarine 39 to 40.
+For this release cycle, we've decided to release an upgrade path before the full distrbution release.
+This should let existing users enjoy the new set of packages in 40 sooner.
+A full blog post detailing changes will be published for the full distrbution release.
+
+## Flagship, GNOME, and KDE Editions
+
+You can use the editon's graphical app store to upgrade your system to 40.
+On Flagship and GNOME, this will be GNOME Software, while on KDE, this will be Plasma Discover.
+
+You might need to update your system normally before the upgrade to 40 shows up in the app store.
+
+## Pantheon Edition
+
+The Pantheon upgrade path isn't ready yet.
+While all of the required packages are in the UM and Terra repositories, the Pantheon desktop enviroment is broken for a variety of reasons.
+We are currently working with upstream and other partners to resolve this, but it's possible that Pantheon may be skipped, deprecated, or defered until mid-cycle.
+If you are interested in contributing to Ultramarine Pantheon, please join [our chats](en/community/community) and let us know!
+
+## Command line
+
+In case the above doesn't work, you can always upgrade through the command line, using `dnf system-upgrade`.
+
+Run the following and follow the prompts:
+
+```sh
+sudo dnf upgrade --refresh
+sudo dnf install dnf-plugin-system-upgrade
+sudo dnf system-upgrade download --releasever=40
+sudo dnf system-upgrade reboot
+```