Hacker News new | ask | show | jobs
by petepete 1758 days ago
I only tested it out a couple of days ago, I'm no expert.

So far it's been plain sailing, I'm already familiar with Yard-style docs and getting everything up and running from the spec/dummy app was really straightforward.

The library I maintain currently uses a home-rolled docs page (https://dfe-digital.github.io/govuk-components/) that needs to be refreshed manually. It's been an 'ok' approach until now but as it's matured we need something that's automated and easier to maintain.

1 comments

Wow that's awesome, I knew GDS had a design system but didn't realise there was a Ruby implementation.

Quick link for others: https://github.com/DFE-Digital/govuk-components

I'm going to take a look through the repo as I'm sure there's some patterns you've found given you're at a much bigger scale. Any hot tips?

This isn't _large scale_ yet, we only have about 15 services using this library. I'm hoping that now we've stabilised and are spending time on making things structurally better (removing tech debt, improving the tests, rewriting the docs) that will rise.

My tip would be to not worry too much about covering every last detail or feature immediately, aim to do what most people need most of the time and release early - then if there's demand for extra stuff add it as you go.

This is amazing! I’d love to chat about what we’re doing with streamlining govt procurement and how your gem could be very useful.
Any time, peter.yates@graphia.co.uk