Repository navigation
Overhaul for the linux-gaming article with Astro starlight features! - #1407
Alexander-Kendrick wants to merge 39 commits into
Conversation
Co-authored-by: Erin O'Connell <erin@system76.com>
Co-authored-by: Erin O'Connell <erin@system76.com>
… new content while updating old content.
Bumps the github-actions group with 5 updates: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `6` | `7` | | [actions/setup-node](https://github.com/actions/setup-node) | `6` | `7` | | [actions/cache](https://github.com/actions/cache) | `5` | `6` | | [xt0rted/markdownlint-problem-matcher](https://github.com/xt0rted/markdownlint-problem-matcher) | `1` | `3` | | [pnpm/action-setup](https://github.com/pnpm/action-setup) | `6.0.9` | `6.0.10` | Updates `actions/checkout` from 6 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v6...v7) Updates `actions/setup-node` from 6 to 7 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v6...v7) Updates `actions/cache` from 5 to 6 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v5...v6) Updates `xt0rted/markdownlint-problem-matcher` from 1 to 3 - [Release notes](https://github.com/xt0rted/markdownlint-problem-matcher/releases) - [Changelog](https://github.com/xt0rted/markdownlint-problem-matcher/blob/main/CHANGELOG.md) - [Commits](xt0rted/markdownlint-problem-matcher@v1...v3) Updates `pnpm/action-setup` from 6.0.9 to 6.0.10 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0ebf471...0977fd9) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/setup-node dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/cache dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: xt0rted/markdownlint-problem-matcher dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: pnpm/action-setup dependency-version: 6.0.10 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the npm-all group with 9 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@astrojs/markdown-satteri](https://github.com/withastro/astro/tree/HEAD/packages/markdown/satteri) | `0.3.5` | `0.4.2` | | [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight) | `0.41.7` | `0.42.5` | | [@iconify-json/simple-icons](https://github.com/iconify/icon-sets) | `1.2.93` | `1.2.98` | | [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `7.2.1` | `7.3.5` | | [astro-icon](https://github.com/natemoo-re/astro-icon/tree/HEAD/packages/core) | `1.1.5` | `1.2.0` | | [sharp](https://github.com/lovell/sharp) | `0.34.5` | `0.35.5` | | [@playwright/cli](https://github.com/microsoft/playwright-cli) | `0.1.18` | `0.1.22` | | [prettier](https://github.com/prettier/prettier) | `3.9.6` | `3.9.9` | | [prettier-plugin-astro](https://github.com/withastro/prettier-plugin-astro) | `0.14.1` | `1.1.0` | Updates `@astrojs/markdown-satteri` from 0.3.5 to 0.4.2 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/markdown/satteri/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/@astrojs/markdown-satteri@0.4.2/packages/markdown/satteri) Updates `@astrojs/starlight` from 0.41.7 to 0.42.5 - [Release notes](https://github.com/withastro/starlight/releases) - [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md) - [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.42.5/packages/starlight) Updates `@iconify-json/simple-icons` from 1.2.93 to 1.2.98 - [Commits](https://github.com/iconify/icon-sets/commits) Updates `astro` from 7.2.1 to 7.3.5 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@7.3.5/packages/astro) Updates `astro-icon` from 1.1.5 to 1.2.0 - [Release notes](https://github.com/natemoo-re/astro-icon/releases) - [Changelog](https://github.com/natemoo-re/astro-icon/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/natemoo-re/astro-icon/commits/astro-icon@1.2.0/packages/core) Updates `sharp` from 0.34.5 to 0.35.5 - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.34.5...v0.35.5) Updates `@playwright/cli` from 0.1.18 to 0.1.22 - [Release notes](https://github.com/microsoft/playwright-cli/releases) - [Commits](microsoft/playwright-cli@v0.1.18...v0.1.22) Updates `prettier` from 3.9.6 to 3.9.9 - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](prettier/prettier@3.9.6...3.9.9) Updates `prettier-plugin-astro` from 0.14.1 to 1.1.0 - [Release notes](https://github.com/withastro/prettier-plugin-astro/releases) - [Changelog](https://github.com/withastro/prettier-plugin-astro/blob/main/CHANGELOG.md) - [Commits](withastro/prettier-plugin-astro@v0.14.1...v1.1.0) --- updated-dependencies: - dependency-name: "@astrojs/markdown-satteri" dependency-version: 0.4.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: "@astrojs/starlight" dependency-version: 0.42.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: "@iconify-json/simple-icons" dependency-version: 1.2.97 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: "@playwright/cli" dependency-version: 0.1.21 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: astro dependency-version: 7.3.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: astro-icon dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: prettier dependency-version: 3.9.8 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: prettier-plugin-astro dependency-version: 1.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-all - dependency-name: sharp dependency-version: 0.35.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the github-actions group with 1 update in the / directory: [pnpm/action-setup](https://github.com/pnpm/action-setup). Updates `pnpm/action-setup` from 6.0.10 to 6.1.0 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0977fd9...ea17c68) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
Socialhappiness
left a comment
There was a problem hiding this comment.
Submitting Review up to line 156. Will continue tomorrow. Love this, great job!
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Co-authored-by: Emma Truong <emma@system76.com>
Socialhappiness
left a comment
There was a problem hiding this comment.
up to line 379! In general, it's not necessary to use I, you, we or our in technical documentation. Adjectives and adverbs should be used sparingly if at all.
| ``` | ||
|
|
||
| Now, let's install `protonup` via `pip`. | ||
| With pipx installed, we now need to ensure that the location pipx is going to be installing our programs is included in our **PATH**. This will allow us to launch applications in the terminal by simply typing their names in and our terminal will understand what we're trying to run. |
There was a problem hiding this comment.
| With pipx installed, we now need to ensure that the location pipx is going to be installing our programs is included in our **PATH**. This will allow us to launch applications in the terminal by simply typing their names in and our terminal will understand what we're trying to run. | |
| Confirm the location pipx is going to be installing programs in is included in your **PATH**. This enables the ability to launch applications in the terminal by simply typing their names and the terminal will understand what you're trying to run. To confirm the location, run the following command; |
modified wording to remove the 'we' type references
| pipx ensurepath | ||
| ``` | ||
|
|
||
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. |
There was a problem hiding this comment.
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. | |
| Close the terminal and launch it once more for the changes to take effect. |
I think this is unnecessary because you explained why we're running that command before running the command, so it doesn't need an after explanation too imo.
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. | ||
|
|
||
| The `protonup` command will be available after a reboot, or you can run the below command to add it to your `PATH` for immediate use. | ||
| Now, let's install **protonup** via **pipx**. |
There was a problem hiding this comment.
| Now, let's install **protonup** via **pipx**. | |
| Install **protonup** via **pipx** with the following command: |
| #### Manage ProtonGE with Protonup | ||
|
|
||
| After <u>Steam</u> is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: | ||
| After **Steam** is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: |
There was a problem hiding this comment.
| After **Steam** is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: | |
| After **Steam** is installed, run **protonup** in a terminal to fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: |
|
|
||
| If you'd like something a little prettier than the default view, we suggest setting your interface to either **Covers** or **Carrousel** mode, starting up Faugus in either **Maximized** or **Fullscreen**, changing the Position of your games to **Bottom**, then setting the checkboxes under **Display** for **Labels**, **Banner**, and **Overview** on. We suggest leaving **Overview** off though if you're using **Covers** view mode. If you have an API Key added, you can then click OK to save your interface and you will get a view that heavily showcases artwork for your games. | ||
|
|
||
| There's other views you can set up too, experiment with what looks nice for you or leave the default settings. |
There was a problem hiding this comment.
| There's other views you can set up too, experiment with what looks nice for you or leave the default settings. | |
| Below are examples of different types of views you can customize. |
|
|
||
| ### Adding a Windows Game | ||
|
|
||
| Now that we have Faugus set up the way we want it, we can add our first game. |
There was a problem hiding this comment.
| Now that we have Faugus set up the way we want it, we can add our first game. | |
| Now that Faugus is set up, it's time to add the first game. |
|
|
||
| Faugus can be used to launch multiple kinds of games, both Windows and Linux. | ||
|
|
||
| Let's start by clicking the Add Game button from the main interface. This is signified with a **+** icon. |
There was a problem hiding this comment.
| Let's start by clicking the Add Game button from the main interface. This is signified with a **+** icon. | |
| Start by clicking the Add Game button from the main interface. This is signified with a **+** icon. |
|
|
||
|  | ||
|
|
||
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. |
There was a problem hiding this comment.
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. | |
| In the New Game/App menu, give the game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. |
we're in the section about installing a windows game, so I removed that first sentence
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. | ||
|
|
||
| <Aside type="tip" title="Scraping Artwork"> | ||
| If you've integrated SteamGridDB into Faugus, it'll suggest game names based on results from the website as you type. You also should be able to simply left click the banner and Cover artwork fields to freely select artwork that is to your liking. |
There was a problem hiding this comment.
| If you've integrated SteamGridDB into Faugus, it'll suggest game names based on results from the website as you type. You also should be able to simply left click the banner and Cover artwork fields to freely select artwork that is to your liking. | |
| If SteamGridDB is integrated into Faugus, it'll suggest game names based on results from the website as you type. Left click the banner and cover artwork fields to freely select artwork. |
Co-authored-by: Emma Truong <emma@system76.com>
Drastically overhauled our gaming article, adding Astro features, new content, updated old content, included section on Lutris, and more.
I've given it a single pass through for proofreading, it is a sizable article now that will likely take some time to go over.