static imports to assets and css files in homepage docs

[janzheng]

I think instead of relative paths, link to assets like this — this makes it way easier to just copy the html from the docs, instead of manually having to hunt down asset links and replacing them.

  <link rel="stylesheet" href="https://esm.sh/jsr/@celine/celine@4.1.0/cell.css" />
  <link rel="stylesheet" href="https://esm.sh/jsr/@celine/libertine@9.1.0/libertine.css" />

[MaxwellBo]

As in, having a giant block with all the imports?

rather than having them split?

[janzheng]

Well, I just mean that right now in the docs code you have relative imports, and I think it'd be easier for adoption if the stylesheet imports were always pointing to the full ESM url.

Otherwise when people copy the source the css is going to break and they'll have to hunt down the ESM url or download the CSS every time.

<link rel="stylesheet" href="celine/cell.css">
<link rel="stylesheet" href="libertine/libertine.css">

to 

  <link rel="stylesheet" href="https://esm.sh/jsr/@celine/celine@4.1.0/cell.css" />
  <link rel="stylesheet" href="https://esm.sh/jsr/@celine/libertine@9.1.0/libertine.css" />

[MaxwellBo]

Hmm good call... almost all deps are absolute except some of the favicon assets and these stylesheets. They've been convenient for development purposes but you're right in that it makes it easier to save the HTML page and get going straight away.

[janzheng]

My copy and paste reflex thanks you!!

[MaxwellBo]

@janzheng just putting these in as comments for now 995621a, unfortunately a bit of a hit to lighthouse scores when pulling from JSR, will investigate

[janzheng]

oh interesting, I guess JSR doesn't do a good job with caching? It's fine as it is now, you can close! Just thought it'd be a slightly better DX