There's a lot of bling "submodules" that might require documentation. Including them inside the same README is beneficial, because it makes the appear on the ublue website too, and their documentation is often not that long.
* fix: terminology
* docs: mention ostree
this is *not* the case on all fedora distros, only the "immutable" / ostree ones
---------
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>
There won't be anything to remove unless the module is called more than once, and if it's called more than once, the user would expect every Flatpak to be in the respective lists, so there's no need to call rm -f on it.
* docs: chore: rn ":" from "Example configuration"
* docs: correct title casing for fonts module title
* docs: document OS_VERSION in example,...
non-copr example for rpmrepos
* docs: remove bling fonts option from bling example
* docs: start yafti README the same way as others
"The yafti module..."
* feat: nerd-fonts modules
* feat: nerd-fonts modules
* feat: fonts module
* fix: fonts module readme
* chore: fonts module readme
* chore: fonts module
* chore: fonts module
* Update nerd-fonts.sh
* Update google-fonts.sh
* chore: scripts
* docs: unify font module grammar with other modules
fixes some misc grammar mistakes and makes documentation more inline with that of other modules
* refactor: move download.sh to root directory
this removes the need of the font source scripts
to have an environment variable with path to the ./scripts directory
making them more portable
* fix: get correct download.sh path
(relative to currently running script)
* chore: rm loop making .sh in scripts/ executable
this is not needed, as download.sh was moved and is called with bash
---------
Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com>