From: Tomas Volf <~@wolfsden.cz>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Luis Felipe <sirgazil@zoho.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: Recommended way of packaging web themes
Date: Thu, 9 Nov 2023 08:56:02 +0100 [thread overview]
Message-ID: <ZUyQklGTtbdF6aiC@ws> (raw)
In-Reply-To: <87h6lv95e9.fsf@lease-up.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On 2023-11-08 15:44:46 -0800, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote:
> Hi Felipe,
>
> On Wed, Nov 08 2023, Luis Felipe wrote:
>
> > I'm looking into packaging the current Guix's website theme
> > [...] 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.
>
> Could you simply publish the resources online (except Javascript, of
> course) so any site can use them?
If that will be done, please try to provide a versioned, well, version as well,
so that subresource integrity can be used.
>
> It would be similar to Google Fonts. [1]
>
> Then I would package the resources being served in such a way that
> anyone can easily set up a second server.
>
> Kind regards
> Felix
>
> [1] https://fonts.google.com/
>
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-09 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 23:10 Recommended way of packaging web themes Luis Felipe
2023-11-08 23:44 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-11-09 7:56 ` Tomas Volf [this message]
2023-11-09 15:11 ` Luis Felipe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZUyQklGTtbdF6aiC@ws \
--to=~@wolfsden.cz \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=sirgazil@zoho.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).