diff --git a/docs/packaging/appstream-metainfo.md b/docs/packaging/appstream-metainfo.md index 7a875839b..9d22fa985 100644 --- a/docs/packaging/appstream-metainfo.md +++ b/docs/packaging/appstream-metainfo.md @@ -32,8 +32,8 @@ There are a few scenarios that Packagers might encounter: | 1 | An application already provides appstream metainfo | Nothing to do | | 2 | An application contains appstream metainfo in the source package but we do not install it | Install the appstream metainfo to `/usr/share/metainfo`. _Example_: [here](https://github.com/getsolus/packages/commit/0a726a53454e7c8a6b0e66de69d59bcc66f0fc19) | | 3 | An application doesn't contain appstream metainfo in the source package but it exists on Flathub | Borrow and tweak the appstream metainfo from the Flathub repo. Encourage upstream project to add it to their source. _Example_: [here](https://github.com/getsolus/packages/commit/da2f65b93f412da43d1db9edbcb08bb90517a0eb) | -| 4 | An application doesn't provide appstream metainfo and it doesn't exist on flathub | See [here](#writing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/414219d8b2ceeabe85178d3a467f81b9131016f4) | -| 5 | Appstream metainfo is provided but composition of it is failing | See [here](#testing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/583b7c742caf50e2f66a70e9b62e9b91566c03f5). | +| 4 | An application doesn't provide appstream metainfo and it doesn't exist on flathub | See [here](#writing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/414219d8b2ceeabe85178d3a467f81b9131016f4) | +| 5 | Appstream metainfo is provided but composition of it is failing | See [here](#testing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/583b7c742caf50e2f66a70e9b62e9b91566c03f5). | AppStream metainfo is to be installed in the `/usr/share/metainfo/` directory. It must be placed in the package which should be installed in order to get the software described by the respective metadata. This means that you might need to move the _.metainfo.xml or _.appdata.xml to the right (sub)package. @@ -55,7 +55,6 @@ In case your AppStream metainfo is describing a desktop application (you can tel - Run a report against the extracted install directory. - For general testing, the following command should be sufficient: ```bash @@ -63,7 +62,7 @@ In case your AppStream metainfo is describing a desktop application (you can tel ``` For more advanced testing, such as media generation, e.g. to test font screenshots get auto-generated, run: - + ```bash appstreamcli compose install/ --hints-dir=hints --media-dir=media --media-baseurl=localhost:8000 --verbose ``` @@ -80,7 +79,7 @@ The `appstreamcli compose` tool will normally give good hints about failures but - A `.desktop` file cannot be matched to the metainfo file. - By default, the `.desktop` file name must match the `` provided in `.xml` file in `/usr/share/metainfo/`. For example, the if you have `org.foobar.my_package` the `.desktop` file should be called `org.foobar.my_package.desktop`. However, there is an exception to this if the metainfo provides a launchable tag. For example, if the metainfo contains `my_package.desktop` then the `.desktop` file can be just called `my_package.desktop`. For more information view the upstream documentation [here](https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Application.html#spec-appdata-introduction). -- No metainfo file is provided. +- No metainfo file is provided. - No appstream metainfo was found in `/usr/share/metainfo/`. - Appstream metainfo may exist in `/usr/share/appdata/` but that path is now obsolete and is no longer read from. - No icon found. @@ -111,19 +110,20 @@ It is not necessary to pass all pedantic warnings, but all errors must be rectif To generate a catalog with appstream generator, a `asgen-config.json` file must be provided. Here is a example configuration file for running against local repositories. + ```json { - "ProjectName": "Solus", - "ArchiveRoot": "/var/lib/solbuild", - "MediaBaseUrl": "http://localhost:8000/export/media", - "HtmlBaseUrl": "http://localhost:8000/export/html", - "Backend": "solus", - "Suites": { - "local": { - "sections": ["main"], - "architectures": ["x86_64"] - } + "ProjectName": "Solus", + "ArchiveRoot": "/var/lib/solbuild", + "MediaBaseUrl": "http://localhost:8000/export/media", + "HtmlBaseUrl": "http://localhost:8000/export/html", + "Backend": "solus", + "Suites": { + "local": { + "sections": ["main"], + "architectures": ["x86_64"] } + } } ``` @@ -134,25 +134,26 @@ To generate the catalog run `appstream-generator run local --verbose`. Depending To view the HTML report, you can start a http server with `python3 -m http.server 8000`, enter `http://localhost:8000/` in your web browser, then navigate to `export/html/`. It can also be ran against a remote repository, here is a sample configuration. + ```json { - "ProjectName": "Solus", - "ArchiveRoot": "https://fastly.getsol.us/repo", - "MediaBaseUrl": "https://appstream.getsol.us/media", - "HtmlBaseUrl": "https://appstream.getsol.us", - "Backend": "solus", - "Suites": { - "gwendraeth": { - "sections": ["main"], - "architectures": ["x86_64"] - }, - "gwendraeth-updates": { - "sections": ["main"], - "architectures": ["x86_64"], - "dataPriority": 10, - "baseSuite": "gwendraeth" - } + "ProjectName": "Solus", + "ArchiveRoot": "https://fastly.getsol.us/repo", + "MediaBaseUrl": "https://appstream.getsol.us/media", + "HtmlBaseUrl": "https://appstream.getsol.us", + "Backend": "solus", + "Suites": { + "gwendraeth": { + "sections": ["main"], + "architectures": ["x86_64"] + }, + "gwendraeth-updates": { + "sections": ["main"], + "architectures": ["x86_64"], + "dataPriority": 10, + "baseSuite": "gwendraeth" } + } } ``` diff --git a/docs/packaging/monitoring.yaml.md b/docs/packaging/monitoring.yaml.md index 7b4863d0f..c608ad7de 100644 --- a/docs/packaging/monitoring.yaml.md +++ b/docs/packaging/monitoring.yaml.md @@ -25,6 +25,7 @@ To add a `monitoring.yaml` file to an existing package you can use the following `go-task add-monitoring` will automatically fill all the fields if a match is found on [release-monitoring.org](https://release-monitoring.org) and [cpe-guesser.cve-search.org](https://cpe-guesser.cve-search.org). ::: + ```bash go-task add-monitoring ``` diff --git a/docs/user/quick-start/boot-management.md b/docs/user/quick-start/boot-management.md index 42a6f5c6b..2b0d72a3a 100644 --- a/docs/user/quick-start/boot-management.md +++ b/docs/user/quick-start/boot-management.md @@ -28,7 +28,7 @@ To make the boot menu appear automatically with a five-second timeout: ## Add kernel parameters -You can add kernel parameters by creating configuration files that `clr-boot-manager` uses when updating kernels. +You can add kernel parameters by creating configuration files that `clr-boot-manager` uses when updating kernels. To add kernel parameters, do the following: @@ -50,7 +50,7 @@ To add kernel parameters, do the following: echo 'nomodeset' | sudo tee /etc/kernel/cmdline.d/40_nomodeset.conf ``` -1. If you want to add multiple parameters, put them on one line with spaces between them in the configuration file. +1. If you want to add multiple parameters, put them on one line with spaces between them in the configuration file. For example: diff --git a/docs/user/quick-start/kernel-management/add-new-kernels.md b/docs/user/quick-start/kernel-management/add-new-kernels.md index f17b03844..ee8f43857 100644 --- a/docs/user/quick-start/kernel-management/add-new-kernels.md +++ b/docs/user/quick-start/kernel-management/add-new-kernels.md @@ -14,14 +14,14 @@ To install and switch to a different kernel branch, follow these steps: - Current kernel ``` - sudo eopkg install linux-current - ``` + sudo eopkg install linux-current + ``` - LTS kernel - - ``` - sudo eopkg install linux-lts - ``` + + ``` + sudo eopkg install linux-lts + ``` 1. Install the necessary kernel modules of the kernel branch you want to try. @@ -52,7 +52,7 @@ To install and switch to a different kernel branch, follow these steps: :::warning Important On systems with UEFI installations, the boot menu doesn't appear by default. - + To display the boot menu, press the Space bar key repeatedly as your computer starts. ::: diff --git a/docs/user/quick-start/kernel-management/remove-old-kernels.md b/docs/user/quick-start/kernel-management/remove-old-kernels.md index 96436df9c..26a7ee59b 100644 --- a/docs/user/quick-start/kernel-management/remove-old-kernels.md +++ b/docs/user/quick-start/kernel-management/remove-old-kernels.md @@ -2,6 +2,7 @@ title: Remove old kernels summary: Manage and remove old kernels to free up space on the boot partition. --- + You might need to remove old kernels for various reasons: - The boot partition is too small for multiple kernel versions @@ -25,11 +26,11 @@ To remove old kernels, do the following: ``` This command displays the version of the currently running kernel. For example: - + ``` 6.6.8-290.current ``` - + Make note of this version. 1. Mount the boot partition. @@ -64,9 +65,9 @@ To remove old kernels, do the following: 1. Remove the kernels you don't need. :::danger Warning - + Never remove the kernel your system is using. This is the version you noted in step 1. - + ::: ```bash @@ -83,4 +84,4 @@ To remove old kernels, do the following: ```bash df -h - ``` \ No newline at end of file + ``` diff --git a/docs/user/software/desktops/index.md b/docs/user/software/desktops/index.md index aa57bf5cd..937617205 100644 --- a/docs/user/software/desktops/index.md +++ b/docs/user/software/desktops/index.md @@ -3,7 +3,7 @@ title: Desktop environments summary: Quick guides on switching between or installing additional desktop environments on Solus --- -Solus offers multiple [desktop environments](https://getsol.us/solus/experiences/): From the feature-rich and modern Budgie to the traditional Xfce experience. +Solus offers multiple [desktop environments](https://getsol.us/solus/experiences/): From the feature-rich and modern Budgie to the traditional Xfce experience. For the best experience, use the Solus ISO of your preferred desktop environment. You can install additional desktop environments later if you want to experiment with different options. @@ -48,4 +48,4 @@ sudo eopkg install -c desktop.xfce Solus MATE is deprecated. For a fast and lightweight desktop experience, use Solus Xfce. -::: \ No newline at end of file +::: diff --git a/docs/user/software/gaming/index.md b/docs/user/software/gaming/index.md index 7bbf1155e..b27535c01 100644 --- a/docs/user/software/gaming/index.md +++ b/docs/user/software/gaming/index.md @@ -5,7 +5,7 @@ summary: Learn about the gaming possibilities on Solus, including Linux, Windows # Gaming -You can play a wide variety of games on Solus: +You can play a wide variety of games on Solus: - Native Linux Games: Run games developed specifically for the Linux platform. - Windows Games: Play many Windows games using compatibility layers like Steam (Proton) and Lutris. @@ -19,4 +19,4 @@ Many games, particularly those run through Steam (Proton) or Lutris, work well o Gaming platforms like Lutris, RetroArch, and Steam are available in the package repository. You can also find many open-source games there, such as Freeciv, OpenTTD, Red Eclipse, and Warzone 2100. -Alternatively, you can also install games and applications from FlatHub. \ No newline at end of file +Alternatively, you can also install games and applications from FlatHub. diff --git a/docs/user/software/gaming/steam.md b/docs/user/software/gaming/steam.md index add38fbf4..32c3adcb0 100644 --- a/docs/user/software/gaming/steam.md +++ b/docs/user/software/gaming/steam.md @@ -5,13 +5,13 @@ summary: Install and configure Steam on Solus # Steam -- To install `steam`, use the Software Center or execute the following command: +- To install `steam`, use the Software Center or execute the following command: - ```bash - sudo eopkg install steam - ``` + ```bash + sudo eopkg install steam + ``` - Steam is also available on Flathub. + Steam is also available on Flathub. ## Running steam games with Nvidia graphics cards @@ -20,7 +20,7 @@ If your system has an Nvidia graphics card, install the 32-bit version of the dr 1. Open **Hardware Drivers** (DoFlicky). 2. Select **Also install 32-bit driver**: - ![DoFlicky UI](./do-flicky-32-bits.png) + ![DoFlicky UI](./do-flicky-32-bits.png) 3. Select the driver of your Nvidia graphics card. 4. Click **Install**. diff --git a/docs/user/software/window-managers/index.md b/docs/user/software/window-managers/index.md index b19d71944..9b8c49a0b 100644 --- a/docs/user/software/window-managers/index.md +++ b/docs/user/software/window-managers/index.md @@ -48,4 +48,4 @@ Labwc is a Wayland-only stacking window manager. To install Labwc on Solus: sudo eopkg install labwc ``` -2. Configure Labwc. For more information, see the [Labwc wiki](https://labwc.github.io/). \ No newline at end of file +2. Configure Labwc. For more information, see the [Labwc wiki](https://labwc.github.io/). diff --git a/docs/user/troubleshooting/boot-rescue/emergency-shell-startup.mdx b/docs/user/troubleshooting/boot-rescue/emergency-shell-startup.mdx index c0ae5811f..481f6df58 100644 --- a/docs/user/troubleshooting/boot-rescue/emergency-shell-startup.mdx +++ b/docs/user/troubleshooting/boot-rescue/emergency-shell-startup.mdx @@ -24,35 +24,36 @@ For this procedure, you need: 1. Shut down your system. 1. Boot from a Solus live USB. -1. Mount the partitions of your Solus system. +1. Mount the partitions of your Solus system. -
- -
+
+ +
-1. Prevent the system from trying to mount unavailable devices. +1. Prevent the system from trying to mount unavailable devices. -
- 1. Edit `/etc/fstab` using `nano`: - ```bash - nano /etc/fstab - ``` - 2. Find all the unavailable devices. - 3. Add the `noauto` option to the line corresponding to the unavailable device. +
+1. Edit `/etc/fstab` using `nano`: + ```bash + nano /etc/fstab + ``` +2. Find all the unavailable devices. +3. Add the `noauto` option to the line corresponding to the unavailable device. - For example: + For example: - ```bash - UUID=XXXXXX /mnt/mydisk exfat noauto,uid=1000,gid=1000,umask=0022 0 0 - ``` - 4. Save the file and restart your system. + ```bash + UUID=XXXXXX /mnt/mydisk exfat noauto,uid=1000,gid=1000,umask=0022 0 0 + ``` -
+ 4. Save the file and restart your system. -1. Unmount all the Solus partitions. -
- -
+
+ +1. Unmount all the Solus partitions. +
+ +
## What to do next diff --git a/docs/user/troubleshooting/boot-rescue/index.md b/docs/user/troubleshooting/boot-rescue/index.md index 51511cd16..91e371e59 100644 --- a/docs/user/troubleshooting/boot-rescue/index.md +++ b/docs/user/troubleshooting/boot-rescue/index.md @@ -20,4 +20,4 @@ Identify your issue by selecting the scenario that matches your situation: - [Solus does not appear in the startup menu](./solus-not-in-boot-menu.md) - [I see an emergency shell or error message during startup](./emergency-shell-startup.mdx) - [My system won't boot after an update](./system-not-working-after-update.mdx) -- [I changed hardware and now my system won't boot](./system-not-working-hardware-change.mdx) \ No newline at end of file +- [I changed hardware and now my system won't boot](./system-not-working-hardware-change.mdx) diff --git a/docs/user/troubleshooting/boot-rescue/snippets/_mount_partitions.mdx b/docs/user/troubleshooting/boot-rescue/snippets/_mount_partitions.mdx index c6a8139f2..a34c68e31 100644 --- a/docs/user/troubleshooting/boot-rescue/snippets/_mount_partitions.mdx +++ b/docs/user/troubleshooting/boot-rescue/snippets/_mount_partitions.mdx @@ -89,7 +89,7 @@ To recover your system, you need to mount the Solus root (`/`) partition and all cryptsetup luksOpen /dev/sdb2 decrypted ``` - 1. Mount the Solus root partition: + 5. Mount the Solus root partition: - If your drive's type is _lvm_ ```bash @@ -111,19 +111,19 @@ To recover your system, you need to mount the Solus root (`/`) partition and all fdisk -o Device,Size,Type -l /dev/sdX ``` - If you have an NVMe drive: - + ```bash fdisk -o Device,Size,Type -l /dev/nvme0nX ``` - + The system displays something similar to this: - + ```bash Device Size Type /dev/sda1 512M EFI System /dev/sda2 111.3G Linux filesystem ``` - + In this case, the EFI system partition is `/dev/sda1` 1. Mount the EFI system partition: diff --git a/docs/user/troubleshooting/boot-rescue/snippets/_unmount_partitions.mdx b/docs/user/troubleshooting/boot-rescue/snippets/_unmount_partitions.mdx index aa2f6acbb..ef90de3a6 100644 --- a/docs/user/troubleshooting/boot-rescue/snippets/_unmount_partitions.mdx +++ b/docs/user/troubleshooting/boot-rescue/snippets/_unmount_partitions.mdx @@ -4,13 +4,13 @@ umount -R /target ``` 3. If your drive is encrypted: - 1. Deactivate your logical volumes and volume groups: - ```bash - lvchange -a n /dev/SolusSystem/Swap - lvchange -a n /dev/SolusSystem/Root - vgchange -a n SolusSystem - ``` - 2. Close the LUKS partition: - ```bash - cryptsetup luksClose decrypted - ``` \ No newline at end of file + 1. Deactivate your logical volumes and volume groups: + ```bash + lvchange -a n /dev/SolusSystem/Swap + lvchange -a n /dev/SolusSystem/Root + vgchange -a n SolusSystem + ``` + 2. Close the LUKS partition: + ```bash + cryptsetup luksClose decrypted + ``` diff --git a/docs/user/troubleshooting/boot-rescue/solus-not-in-boot-menu.md b/docs/user/troubleshooting/boot-rescue/solus-not-in-boot-menu.md index 051a94b0f..9e80d16ec 100644 --- a/docs/user/troubleshooting/boot-rescue/solus-not-in-boot-menu.md +++ b/docs/user/troubleshooting/boot-rescue/solus-not-in-boot-menu.md @@ -5,6 +5,7 @@ After a software update, Solus might disappear from the startup menu. This situation commonly occurs on systems using a legacy startup method (non-UEFI systems) where another Linux distribution owns the startup manager (such as GRUB). ## Procedure -- To restore access to Solus, access the other operating system and update the startup manager. - For more information, check the documentation of your distribution. \ No newline at end of file +- To restore access to Solus, access the other operating system and update the startup manager. + + For more information, check the documentation of your distribution. diff --git a/docs/user/troubleshooting/boot-rescue/system-not-working-after-update.mdx b/docs/user/troubleshooting/boot-rescue/system-not-working-after-update.mdx index 0d14f22b6..deacaeeb6 100644 --- a/docs/user/troubleshooting/boot-rescue/system-not-working-after-update.mdx +++ b/docs/user/troubleshooting/boot-rescue/system-not-working-after-update.mdx @@ -19,21 +19,22 @@ For this procedure, you need: ## Procedure -1. Shut down your system. -1. Boot from a Solus live USB. +1. Shut down your system. +1. Boot from a Solus live USB. 1. Mount the partitions of your Solus system.
-1. Check the chroot environment has internet connection. +1. Check the chroot environment has internet connection. +
- 1. Connect your computer to the internet. - 2. Run `ping -c 4 google.com` in the chroot environment. - + 1. Connect your computer to the internet. + 2. Run `ping -c 4 google.com` in the chroot environment. + If the chroot environment has internet connection, the system displays the following: - + ```bash PING google.com (142.250.196.206) 56(84) bytes of data. 64 bytes from nctsaa-ac-in-f14.1e100.net (142.250.196.206): icmp_seq=1 ttl=115 time=4.26 ms @@ -46,68 +47,70 @@ For this procedure, you need: ``` 3. If the chroot environment *does not* have an internet connection: 1. Exit the chroot environment: - + ```bash exit ``` - + 2. Run the following commands: - + ```bash cp /run/systemd/resolve/stub-resolv.conf /target/run/systemd/resolve/ cd /target/etc ln -s ../run/systemd/resolve/stub-resolv.conf /target/etc/resolv.conf ``` - + 3. Go back to the chroot environment: ```bash chroot /target ``` - + 4. Test the internet connection again. - +
-1. Repair your Solus installation. +1. Repair your Solus installation. +
- Follow the appropriate steps depending on your situation: - + Follow the appropriate steps depending on your situation: +
My system stopped working after a *failed* update. 1. Rebuild the package database: - + ```bash sudo eopkg rebuild-db ``` - + 2. Update your system: - + ```bash sudo eopkg up ``` - + 3. Check if your system still has broken packages: - + ```bash sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall ``` - + If you see output that starts with "Usage", the system has no broken packages.
- +
My system stopped working after a *successful* update - + See [Rollback](/docs/user/package-management/history-and-rollback#rollback).
+
-1. Unmount all the Solus partitions. +1. Unmount all the Solus partitions. -
- -
+
+ +
## What to do next diff --git a/docs/user/troubleshooting/boot-rescue/system-not-working-hardware-change.mdx b/docs/user/troubleshooting/boot-rescue/system-not-working-hardware-change.mdx index 734351fd1..9cdb5b840 100644 --- a/docs/user/troubleshooting/boot-rescue/system-not-working-hardware-change.mdx +++ b/docs/user/troubleshooting/boot-rescue/system-not-working-hardware-change.mdx @@ -16,34 +16,35 @@ For this procedure, you need: ## Procedure -1. Shut down your system. -1. Boot from a Solus live USB. +1. Shut down your system. +1. Boot from a Solus live USB. 1. Mount the partitions of your Solus system.
-1. Update the system configuration to address the hardware changes. +1. Update the system configuration to address the hardware changes. +
- 1. Re-run system-wide configuration triggers - + 1. Re-run system-wide configuration triggers + ```bash sudo usysconf run -f ``` - - 2. If you use an UEFI system, update the boot entries for your EFI menu: - ```bash - sudo clr-boot-manager update - ``` -
-1. Unmount all the Solus partitions. + 2. If you use an UEFI system, update the boot entries for your EFI menu: + `bash + sudo clr-boot-manager update + ` + + +1. Unmount all the Solus partitions. -
- -
+
+ +
## What to do next - \ No newline at end of file + diff --git a/docs/user/troubleshooting/plasma.mdx b/docs/user/troubleshooting/plasma.mdx index 537ad45ae..b3291f85b 100644 --- a/docs/user/troubleshooting/plasma.mdx +++ b/docs/user/troubleshooting/plasma.mdx @@ -50,7 +50,6 @@ You should not be logged into your Plasma session while deleting the cache files 1. While still logged into your Plasma session, go to your home directory: - ```bash cd ``` @@ -71,7 +70,7 @@ The commands create a copy of the folders. Each copy has the `.bak` extension (E 1. Mount the partitions of your Solus system.
- +
1. Change to your user's directory in the chrooted environment: @@ -99,7 +98,7 @@ The commands create a copy of the folders. Each copy has the `.bak` extension (E ::: 1. Remove the various caches that Plasma uses. - + Execute the following commands: ```bash @@ -107,13 +106,13 @@ The commands create a copy of the folders. Each copy has the `.bak` extension (E rm -rf .cache/org.kde.dirmodel-qml.kcache rm -rf .cache/kioexec/ .cache/krunner/ .cache/ksycoca5* rm -rf .cache/krunnerbookmarkrunnerfirefoxdbfile.sqlite - + cd ../.local/ rm -rf kate/ kded5/ klipper/ knewstuff3/ kscreen/ konsole/ kwalletd/ ksysguard/ kmail2/ kcookiejar/ kactivitymanagerd/ - + cd ../share/ rm -rf dolphin kate kcookiejar kded5 keyrings klipper kmail2 knewstuff3 konsole kscreen ksysguard kwalletd kxmlgui5 plasma_engine_comic plasma plasma_notes org.kde.gwenview - + cd ../.config/ rm -f plasma* rm -rf kde* akonadi* KDE kconf_updaterc baloo* dolphinrc drkonqirc gwenviewrc kmail2rc k*rc katemetainfos @@ -124,7 +123,7 @@ The commands create a copy of the folders. Each copy has the `.bak` extension (E 1. If you experience system instability, restore the previously backed up folders. To restore an entire directory: - + ```bash cp -rav .kde.bak/share/config/ .kde/share/config ``` diff --git a/src/components/Person.tsx b/src/components/Person.tsx index 0eb7f6f95..8b2675d7f 100644 --- a/src/components/Person.tsx +++ b/src/components/Person.tsx @@ -60,9 +60,7 @@ export const Person = ({ embeddedIn, isBadge = false, onAvatarClick, person, sx {!isBadge && ( <> - - {person.description} - + {person.description} {person.matrix && Matrix: {person.matrix}} )} diff --git a/src/components/Teams.tsx b/src/components/Teams.tsx index 31e140585..3f091be9d 100644 --- a/src/components/Teams.tsx +++ b/src/components/Teams.tsx @@ -36,7 +36,9 @@ export const TeamMember = ({ haveSupplementalInfo, teamName, person, supplementa person={person} sx={{ minWidth: 240 }} /> - {haveSupplementalInfo && {supplementalInfo}} + {haveSupplementalInfo && ( + {supplementalInfo} + )} ); }; diff --git a/src/data/teams.ts b/src/data/teams.ts index c227ab7f2..c9eba19bb 100644 --- a/src/data/teams.ts +++ b/src/data/teams.ts @@ -14,8 +14,7 @@ export const Teams: Team[] = [ name: "Admin Team", }, { - description: - "This team has push access to all Solus repositories, and makes general decisions about the project.", + description: "This team has push access to all Solus repositories, and makes general decisions about the project.", members: [ ["ReillyBrogan", null], ["EvanMaddock", null],