[0] https://www.dataprotection.ie/en/organisations/know-your-obl...
1,065 karma · joined August 20, 2022
Ambient ScotRail Beats: https://matteason.co.uk/scotbeats
matteason.co.uk Twitter: @MattEason Email: hn@matteason.co.uk
[0] https://www.dataprotection.ie/en/organisations/know-your-obl...
I've got vague plans to add generative music to Ambiphone and I've been using Ableton so far but I think this will be a really useful sketchpad for experimenting with sounds and patterns
https://design-system.service.gov.uk/components/exit-this-pa...
Yeah the target for this definitely isn't the regular transactional GOV.UK services. I've added a note at the top of the installation guide:
> GOV.UK Vue (or any JavaScript library) might not be suitable for your project if it's a standard transactional government service. Make sure you read the guidance on progressive enhancement and building more complex services before starting. GOV.UK Vue is designed to be used in more complex services, like interactive mapping, or internal tools where you've determined that JavaScript is acceptable.
GDS are also currently doing exploratory work to investigate how Frontend can be more closely integrated with React/Vue/Svelte/Angular etc, so it's definitely not verboten: https://github.com/alphagov/govuk-frontend/issues/5172
SSR/SSG is supported (the docs website is an SSG Nuxt app) but I need to do some work to improve how it works for certain components to ensure the state they're first rendered in is usable on its own (eg defaulting accordion components to open on the server-rendered version)
GOV.UK Vue isn't intended for normal, bread-and-butter transactional services (usually a series of form pages) but for things like more complex internal tools, dashboards, mapping etc which would be using JS to provide interactivity
Frontend updates are often CSS-only, so those will be taken care of by the consuming project updating it. For markup changes and new components, that's a manual process on my side. Markup changes are usually minor and new components are rare, so it's not too much effort to keep up. I work on GOV.UK services in my day job so I've always got an eye on what's coming up.
Because it's so heavily tested for accessibility it makes sense to use in those kinds of contexts where accessibility is a very high priority.
GOV.UK Frontend can be heavily customised via Sass variables (eg the font stack in [1]) so the components don't have to look like GOV.UK if you don't want them to. GOV.UK Vue pulls all its styling from Frontend so it's as customisable as Frontend is.
[0] https://www.rnib.org.uk/living-with-sight-loss/assistive-aid...
[1] https://github.com/alphagov/govuk-frontend/blob/main/package...
Plenty of non-gov organisations use various bits of it, for example the breadcrumbs and accordion on [1]
[0] https://www.gov.uk/service-manual/design/making-your-service...
[1] https://www.rnib.org.uk/living-with-sight-loss/assistive-aid...
Edit: Re naming - GOV.UK [Thing] is an established convention for community tools, as shown on [3]. GDS are aware of the project.
[3] https://design-system.service.gov.uk/community/resources-and...
[0] https://github.com/alphagov/govuk-frontend
[1] https://design-system.service.gov.uk/
[2] https://design-system.service.gov.uk/community/resources-and...
I'd make it fetch the meta tags and image using the user agent string of the services you're showing previews for. For example, Twitter/X fetches meta tags with a user agent string of Twitterbot/1.0. Some sites may serve different content to different services in order to optimise the image for display on that service.
It also looks like your API may not be looking at Twitter-specific meta tags [0], as it just returns one set of metadata that's used by every preview. For example on https://govukvue.org I use the 'summary' card format, which shows a small image with the name and description beside it. But your tool renders it as if it's a 'summary_large_image'.
[0] https://developer.x.com/en/docs/x-for-websites/cards/overvie...
I'd be really interested to hear how you get on with this - I've been wanting to add these kinds of feeds to https://ambiph.one but it looks like they're not issuing new licenses for the feeds and the Calls API looks like it's write-only from the docs?
Just a heads up, a handful of your Read More links on the homepage are broken
[0] https://en.wikipedia.org/wiki/Windows_DreamScene?useskin=vec...
The kicker is that your PNR number and surname are encoded in the barcode on your boarding pass, easily scannable with a phone app. If you ever post a boarding pass online you're unintentionally doxxing yourself and potentially letting people screw with your flights.
I've seen celebrities do this, and during the Cloudstrike outage one tech CEO posted his handwritten boarding pass on Twitter with the PNR in full view.
https://krebsonsecurity.com/2017/08/why-its-still-a-bad-idea...
https://news.ycombinator.com/item?id=33207685
https://news.ycombinator.com/item?id=26165357
I wonder how big your site has to be to earn a spot in that file when you hit a Safari bug. Don't suppose Apple publish the criteria anywhere?
[0] https://github.com/WebKit/WebKit/blob/84ae355619354ee1bfa7da...
One of the references is for a Mercedes system that uses ultrasound
[0] https://old.reddit.com/r/TaylorSwift/comments/17iv3r2/for_pe...
The usual flow for sites where you can create custom products is that you can get into the designer with no login and you only need to enter your details at checkout.
There's nothing useful on the landing page that would convince me to sign up - what kind of cakes can I order? What locations do you cover? What kind of designs? Can I add my own images or pick from a library or both? Do you do allergy-friendly cakes? What are your lead times? Pricing? That's all the kind of stuff I'd need to know before worrying about the design
It's an interesting technique though. I'm building a notes app at the moment and someone's requested it as an accessibility feature. Do you use the extension day-to-day? Do you find it makes a difference?
Small nitpick, the download button takes you to a Chrome webstore page with the parameter 'hl=pt-BR' in the URL, which forces the page to show in Brazilian Portugese rather than the user's language
I've participated in some user research with the team building it and I've also designed GOV.UK services pre-One Login that needed to verify people's identity. It's obviously a very difficult problem to solve when there's no universal central ID database. The people working on it are definitely cognizant of the failure of Verify and they're keen not to repeat it.
I do hate the 'GOV.UK One Login' name though. It's previously been called 'GOV.UK Account' and 'GOV.UK Sign In', I'm not sure what was wrong with either of those.
I built a much more basic web-based version of it, using Twitter posts, a few years ago. It stopped working when the Twitter API became paid-for, but I screen-recorded a demo of it: https://www.youtube.com/watch?v=GaRenG89G9g