Recommended way of packaging web themes

[Luis Felipe <sirgazil@zoho.com>]

[-- Attachment #1.1.1: Type: text/plain, Size: 1690 bytes --]

Hi,

With "web theme" I mean a directory containing CSS, JavaScript, images 
and other files that define a particular look and feel for a website, 
web application or other kinds of products that use web technologies.

For example, I'm looking into packaging the current Guix's website theme 
and a new theme that I've been planning to develop (based on the 
former). If these were packaged, I think it would be easier for other 
Guix websites and services (e.g. CI, QA, DATA) to use them and hopefully 
achieve a more uniform look and feel for the network of Guix web fronts.

I've experimented a bit and packaged both themes:

https://codeberg.org/luis-felipe/guix-channel-x/src/branch/trunk/luflac-x/packages/web-themes.scm

Once installed, I can access both themes from a custom path indicated by 
a non-standard environment variable (WEB_THEMES_PATH, currently set by 
the defined packages):

#+begin_example
❯ guix shell -L luflac-x guile guix-website-theme-initial 
guix-website-theme-aureus
❯ guile
...
 > (getenv "WEB_THEMES_PATH")
$1 = "/gnu/store/gc0szk5h3s45d605ikzyxxxc4z2b9l3l-profile/www/themes"
 > (define guix-icon-path (string-append $1 "/aureus/base/img/icon.svg"))
 > (file-exists? guix-icon-path)
$2 = #t
#+end_example

However, while this seems to work alright, I'm not confident it is the 
right thing to do...

How would you recommend packaging these kinds of themes?

Are there any standard paths and environment variables for web themes? 
Or should one use Freedesktop.org's XDG_DATA_DIRS and their specified 
locations instead?

Thanks in advance,

-- 
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]