Repository navigation
feat(landing): add the Flathub install tab and match the published site - #162
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brings
landing/in line with what is already deployed at https://scribe.cloudless.club.The site was updated straight on the server, so the repository still carried the version from #150. A deploy from a clean clone would have silently reverted the Flathub tab.
What changed
flatpak install flathub io.github.gnacho.Scribeandflatpak run io.github.gnacho.Scribe.installUrlplussameAsfor Flathub in the JSON-LD.main.jsgainedlink,linkTextandlinkTextEn, andupdateInstall()rewrites the href and label. Flathub goes to the listing, AUR to the AUR package and deb, rpm and AppImage to the latest release.?v=20261027afor the CSS,main.jsand thei18n.jsimport.Notes
No new deploy is needed: every file in
landing/after this PR is byte for byte what the server is serving, which is how it was verified (fetching the live HTML,main.js,i18n.js,style.cssandfonts.cssand diffing them against the working tree).