feat: remove images page and link to ISOs instead (#714)

* feat: remove images page and link to ISOs instead * chore: Use image picker link for Bazzite --------- Co-authored-by: Kyle Gospodnetich <[email protected]>
ublue-os · Feb 23, 2024 · 72e1b08 · 72e1b08
1 parent 870d655
commit 72e1b08
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 73 deletions.
diff --git a/docs/installation.md b/docs/installation.md
@@ -7,85 +7,27 @@ Notably:
 - Dual boot configurations are not supported. We recommend using your PC's BIOS/UEFI boot menu for dual boot configuration so that each OS has its own disk.
 - Manual partitioning is not supported.
 
-!!! Warning "This ISO is experimental"
+## Bazzite
 
-    This method of consuming Fedora is new, and will not be integrated into Fedora until at least F39. Though this method is typically more reliable than traditional distributions, take care to [read the user guide](https://docs.fedoraproject.org/en-US/fedora-silverblue/) and manage your expectations accordingly. As with all operating systems, make a point to back up the data you care about! 
+Bazzite is a custom image built on Fedora Atomic technology that brings the best of Linux gaming to all of your devices (yep, even your favorite handheld). Featuring a rock-solid base with automatic updates and ninety days of rollbacks.
 
-## Installation Instructions
+- Check [the Bazzite image picker](https://bazzite.gg#image-picker) for download instructions
 
-!!! Warning "There is a known issue with Ventoy"
+## Bluefin
 
-    We are aware of an issue where booting from the ISO with Ventoy leads to a black screen with a cursor and nothing happening. This is due to an upstream bug with Anaconda and the way Ventoy sets up loop mounts. We are preparing a workaround to enable this workflow. In the meantime, please do not create a new issue on GitHub. You can react with a thumbs up on this [issue](https://github.com/ublue-os/main/issues/108) so we can track how many people want this feature.
+The next generation Linux workstation, designed for reliability, performance, and sustainability.
 
-Each Universal Blue image can be installed from the boot menu of the installation ISO. If you're using an existing Fedora Silverblue/Kinoite system check out the [image page](/images) for rebasing information (you don't need to reinstall).
+- Check [the Bluefin documentation](https://universal-blue.discourse.group/docs?topic=41) for image download instructions
 
-For new systems, follow the instructions below:
+## Generating your own custom ISO of a main image
 
-[Download the ISO :fontawesome-solid-heart:](https://github.com/ublue-os/main/releases){ .md-button .md-button--primary }
+Use any machine with `docker` to generate an ISO of a main image:
 
-1. Use the [Fedora Media Writer](https://flathub.org/apps/details/org.fedoraproject.MediaWriter) to write the ISO to a USB stick.
-    Mac and Windows users can [download it here](https://getfedora.org/en/workstation/download/). Or use a tool of your choice.
+    docker run --rm --privileged --volume .:/isogenerator/output -e VERSION=39 -e IMAGE_NAME=kinoite-nvidia -e IMAGE_TAG=latest -e VARIANT=Silverblue ghcr.io/ublue-os/isogenerator:39
 
-2. Select the image you want to install from the boot menu. The `main` images will work on systems with Intel and AMD GPUs, and the images tagged with `nvidia` include the proper drivers:
-    ![installer](https://user-images.githubusercontent.com/1264109/230446211-a0c4b2e8-2d31-44cb-9179-202f4b9fc52d.png)
-    ![installer2](https://user-images.githubusercontent.com/1264109/230446224-ae43322f-9e4d-4a17-8133-a8bf6def3e64.png)
+You can find the list of published images on [the GitHub packages page](https://github.com/orgs/ublue-os/packages)
 
-    !!! Info "Disk check"
+Check the [isogenerator documentation](https://github.com/ublue-os/isogenerator) for more information on generating your own ISO image.
 
-        The installer will do an integrity check after you've made a selection, this is normal but can be skipped by hitting Escape. The disk detection step might also take longer than expected.
+
 
-3. If you are familiar with Anaconda there are a few changes you might notice:
-
-    ![image](https://user-images.githubusercontent.com/1264109/228308230-4cd981f7-d524-44c3-80ff-49e1b62e58fd.png)
-
-4. "Kickstart Insufficient" is expected, select that item and select the disk to install to and click Done at the top left of the screen. 
-    User creation is also done at this step instead of first boot.
-
-5. Ensure the machine is on the network by configuring that, otherwise you will get an error (see below)!
-
-6. Select each screen with a warning triangle and make the selection you want until the screen looks similar to this:
-
-    ![image](https://user-images.githubusercontent.com/1264109/228308903-d3289faf-8d53-4999-9296-2facc364d07b.png)
-
-7. Continue on with the installation
-
-    !!! Warning
-
-        The progress bar during installation will start, but will not progress until towards the end of installation. Depending on the image size this might take a long time. This may appear as though the installation is stalled.  
-
-    ![image](https://user-images.githubusercontent.com/1264109/228309296-993f7058-7bc7-4157-b1da-3fe908889e37.png)
-
-    When the installation is complete it will ask you to reboot, then you're done!
-
-## Other gotchas
-
-- Reminder: this is a `netinstaller`!
-- If the network connection is spotty, the installation download of the image might stall or time out, resulting in an error message (see [bottom of page](#reporting-issues)).
-    - Retrying the installation might help depending on network conditions.
-    - Using an ethernet connection is usually more reliable.
-- The generated USB stick will always pull the latest image, you shouldn't need to generate a new USB stick often.
-- We are looking for volunteers to help generate proper "offline" ISOs.
-- If you're still having problems with the ISO you can always [install Fedora Silverblue](https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/) and then rebase to one of [our images](/images).
-
-## Secure Boot
-
-If you choose to install an nvidia variant and have Secure Boot enabled, the installer will automatically use `mokutil` to import the ublue-os nvidia module signing key as a Machine Owner Key (MOK) in your UEFI secure boot database.
-
-During the post-install reboot, your system will prompt to verify enrollment of the key.
-
-The installer uses a default password for MOK enrollment: **ublue-os**
-
-!!! Warning
-    If you use `secureboot` and do not enroll the MOK, you will boot to a blank screen, as nouveau has been disabled since nvidia drivers were installed but unable to load without the MOK.
-
-## Video Overview
-
-This video goes over what installation should look like, but, note, the video refers to multiple ISOs. There is now just one ISO image used to boot. The rest of the installation looks the same as the video.
-
-![type:video](https://www.youtube.com/embed/SaPxDJtjoB8)
-
-## Reporting Issues
-
-Please [file an issue](https://github.com/ublue-os/main/issues) if you encounter any problems. An error screen usually looks like this:  
-
-![229818630-cb7e4fb5-42a4-4890-8e75-f92d0ea8dd5b](https://user-images.githubusercontent.com/1264109/230695149-b2c30851-ead0-46f5-8c28-e6aed2b4f6de.png)
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -102,9 +102,6 @@ plugins:
 nav:
   - Home: index.md
   - Installation: installation.md
-  - Images:
-      - Full Image List: images.md
-      - Main Images: images/main.md
   - Community:
       - Code of Conduct: CODE_OF_CONDUCT.md
       - Discord Chat: https://discord.gg/WEu6BdFEtp