Sharing and comments

Share this page


  1. Comment by SEMfuze posted on

    The reactions diagram is pretty cool.

  2. Comment by Paul Downey posted on

    All our code, apart from infrastructure and some sensitive projects, is open source and on GitHub: and our approach for coding in the open is explained in the service manual:

    • Replies to Paul Downey>

      Comment by Rowan posted on

      Excellent, thanks Paul! Will check that out

  3. Comment by Rowan posted on

    Your approach is admirable, but for a site like ours (Transport Scotland) we only have a small team and a very limited budget to spend on enhancements. Do you have any plans to share your coding or platforms with other public sector webmasters?

  4. Comment by Tim Blackwell posted on

    Will you have an internal URL shortening service? Or better, a unique, short non-repudiable identifier for each document published on, ideally supporting versioning and compound documents. Perhaps you have such things already?

    • Replies to Tim Blackwell>

      Comment by Paul Downey posted on

      We have in some cases created a 'friendly URL' (FURL) for popular pages, e.g." . Non-repudiation has a number of different meanings, but as the post outlines, our principles dictate we have to identify a clear user-need before building something new, I suspect many of these feature are answered by GOV.UK having stable, quotable URLs, with redirects when they change.

  5. Comment by What the federal budget illustrates about social media in government posted on

    [...] policies. (NOBODY in Canada’s government would write a blog post and title it “Widgets, badges and blog bling.” Trust [...]

  6. Comment by kriscoverdale posted on

    "By embedding third party code in GOV.UK we also tie our integrity to that service. If the service is compromised in an attack, shut down, changed without notice or taken over by a new provider we could be left with broken functionality, or missing or inappropriate content on GOV.UK."

    Surely your integrity is tied to that service from the decision to "use of 3rd party web apps to help curate and host content". If YouTube was shutdown, the video will be unavailable, regardless of how you choose to embed it?

    • Replies to kriscoverdale>

      Comment by Paul Downey posted on

      YouTube is one of the few cases where GOV.UK hosts content on a third-party site, otherwise the data behind the content will be hosted on GOV.UK with links out to view that data elsewhere on The Web, as with the mapping example.

  7. Comment by Andy Mabbett posted on

    Google Maps? Why not OpenStreetMap?

    • Replies to Andy Mabbett>

      Comment by Paul Downey posted on


      the approach for mapping isn't tied to Google Maps, rather illustrates using one of a number of services to build mapping data, with a static image which links to the data in an number of different formats and links to the map in a number of different services including OSM.

      However my sketch does use KML as an example open format, mainly because it supports points, shapes and HTML.


  8. Comment by Gavin Bell (@zzgavin) posted on

    This all looks like a sensible approach to supporting a wide range of providers and allowing the information to persist beyond the life of a commercial API or company. Can you comment on any progress that GDS have made with a matching policy for badging GOV.UK out onto other sites?
    thanks Gavin

    • Replies to Gavin Bell (@zzgavin)>

      Comment by Paul Downey posted on

      I've an example for publishing a slideshow, actually a single page with full-bleed images, which has a link for embedding in other pages. We should definitely enable similar extensions for maps and other content: