Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GOV.UK proposals #101

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions example/README.md

This file was deleted.

Binary file removed example/profile_picture.jpg
Binary file not shown.
20 changes: 20 additions & 0 deletions not_that_kind_of_panopticon/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
# Not that kind of Panopticon (or how we're publishing the government in Ruby)

In January 2012, a team of in-house Ruby developers at the Government Digital Service released the first iteration of the [GOV.UK beta](https://www.gov.uk/), showing how a single domain for the UK government could operate for citizens. This was soon followed by the [INSIDE GOVERNMENT beta](https://www.gov.uk/government/), showing how specialist departmental content could belong on GOV.UK, and later this year, content for business owners will also be available on GOV.UK.

To meet the needs of citizens, business users and those looking for specialist content, GOV.UK demands a solid publishing platform at its core. This talk will cover our approach to building and evolving a Rails publishing platform which can scale across propositions, provide a full editorial workflow process, and can make accountable each item of content to an user need we have identified. We'll also take a look at how we've iterated our data model to simplify our platform, and discuss a few of the 'growing pains' we've experienced in the process, and how we dealt with them.

## Jordan Hatch

Jordan Hatch is a young-ish Ruby developer, almost based in London. He's a developer at the Government Digital Service, working on the cross-proposition team for the GOV.UK beta. He tweets at [@1jh](http://twitter.com/1jh).

![Profile picture](http://farm7.staticflickr.com/6141/6012987592_f92e29cf92_b_d.jpg)

## James Stewart

James Stewart is a software developer based in London with his wife and two small kids. Having been building things for the web since the mid-90s, he was technical lead for Alpha.gov.uk and now works as a technical architect for the Government Digital Service helping shape a new open-source platform for the UK Government.

![Profile picture](https://github.com/jystewart/call-for-proposals/raw/master/rebuilding_government/profile_picture.jpg)

- [Blog](http://jystewart.net)
- [Twitter](http://twitter.com/jystewart)
23 changes: 23 additions & 0 deletions rebuilding_government/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Rebuilding government (with a little help from Ruby)

Starting in February 2010 a small group of developers, designers and product thinkers began work on [Alpha.gov.uk](http://www.alpha.gov.uk), demonstrating what a new, simplified and unified website for the UK government might look and feel like. Now with [GOV.UK](https://www.gov.uk) we're showing how it could operate, working with the intention that this will become the definitive government web presence. It's almost all ruby, largely open source and developed out in the open on github (where else?).

A key design principle has been "tools over content"; with an in-house team we can be a lot more creative than simply implementing a content management system. Instead we're focussed on providing citizens with clear, simple, appropriate guidance and utilities. That's had a huge impact on our architecture, sometimes good and sometimes less so. This talk will explore some of the trade-offs and what we're doing to simplify in the midst of growing attention, requirements and pace.

Along the way I'll also cover some of the lessons learned from scaling our team fast, baking in security practices, and practicing continuous delivery in a unique and especially risk-averse world.

## James Stewart

James Stewart is a software developer based in London with his wife and two small kids. Having been building things for the web since the mid-90s, he was technical lead for Alpha.gov.uk and now works as a technical architect for the Government Digital Service helping shape a new open-source platform for the UK Government.

![Profile picture](https://github.com/jystewart/call-for-proposals/raw/master/rebuilding_government/profile_picture.jpg)

- [Blog](http://jystewart.net)
- [Twitter](http://twitter.com/jystewart)


## Jordan Hatch

Jordan Hatch is a young-ish Ruby developer, almost based in London. He's a developer at the Government Digital Service, working on the cross-proposition team for the GOV.UK beta. He tweets at [@1jh](http://twitter.com/1jh).

![Profile picture](http://farm7.staticflickr.com/6141/6012987592_f92e29cf92_b_d.jpg)
Binary file added rebuilding_government/profile_picture.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.