zero-to-nix
zero-to-nix copied to clipboard
Migrate site to Astro
Deploy Preview for zero-to-nix ready!
| Name | Link |
|---|---|
| Latest commit | 29ee926f50b4a87e732d028f3ec171ede247d018 |
| Latest deploy log | https://app.netlify.com/sites/zero-to-nix/deploys/674514750dd55b00086529a9 |
| Deploy Preview | https://deploy-preview-346--zero-to-nix.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
holy guacamole
Off the bat, WOW!
I noticed the rounded pill-buttons change color on hover before they're actually clickable:
@grahamc Fixed
The feedback widget needs a bit of touch-ups:
old:
new:
Note this is a problem on both sites, and I'm not real fussed, but I noticed it expands when typing:
...and with a narrower viewport, it gets a bit weirder:
This is looking good to me. I'm still not seeing the cookie consent popup, but beyond that, I don't see any obvious problems. I think we should move forward with a merge as soon as the consent window comes up.
I cannot for the life of me get it to work, so this will probably be a while
Have you poked around this repo? https://github.com/jop-software/astro-cookieconsent/blob/main/src/main.ts
...poking around a bit I noticed a weird flash of content on every refresh, which turns out to be all the user-initiated things:
...maybe that's a clue?
@grahamc There isn't really a way out of the flash of unstyled content with dark mode and a fully static site. Vue + iles has some JS magic built into it that prevents that but we don't have access to that here.
As for the cookie consent plugin, I don't see a way to integrate that with Posthog.
@lucperkins I think if you pin posthog to just before v1.136.0 our posthog conditions will work correctly.
@grahamc Alas, that doesn't work either. I just cannot get posthog.has_opted_in_capturing() || posthog.has_opted_out_capturing() to be anything but true no matter what I do. Very frustrating. Gonna keep trying.
@lucperkins I think it is because posthog is getting its .js from us.i.posthog.com, instead of the bundled version we've pinned. Is that possible?