Skip to content

results-2018.md

Latest commit

 

History

History
203 lines (181 loc) · 5.07 KB

results-2018.md

File metadata and controls

203 lines (181 loc) · 5.07 KB

Government frontend survey results 2018

Question 1: What department, agency or organisation do you work in?

Answers

Name Count Percentage
MOJ 15 22.7%
GDS 12 18.2%
DWP 8 12.1%
HMRC 6 9.1%
Home Office 6 9.1%
DfE 2 3.0%
DIT 2 3.0%
Cabinet Office 2 3.0%
Met Office 1 1.5%
DEFRA 1 1.5%
The Insolvency Service 1 1.5%
NCA 1 1.5%
Registers of Scotland 1 1.5%
DVSA 1 1.5%
NHS 1 1.5%
DfE / ESFA 1 1.5%
HM Land Registry 1 1.5%
Environment Agency 1 1.5%
Office for National Statistics 1 1.5%
Local authority 1 1.5%
Gambling Commission 1 1.5%

Question 2: What is your main role on this project?

Answers

Name Count Percentage
Frontend development 28 41.8%
Full stack development 21 31.3%
Design 7 10.4%
Backend development 7 10.4%
Technical architect 3 4.5%
Other 1 1.5%

Question 3: What is the frontend of your project built upon?

Answers

Name Count Percentage
Node.js 24 27.6%
Ruby on Rails 15 17.2%
React 9 10.3%
Python 9 10.3%
Scala and Play 8 9.2%
Java 6 6.9%
Vue.js 3 3.4%
PHP 3 3.4%
jQuery 2 2.3%
Don't know 1 1.1%
Razor / .NetCore 1 1.1%
.net 1 1.1%
Dojo 1 1.1%
Riot 1 1.1%
Vanilla JS 1 1.1%
Blade 1 1.1%
Microsoft Dynamics 1 1.1%

Question 4: What templating languages do you use on this project?

Answers

Name Count Percentage
Nunjucks 21 22.6%
ERB 9 9.7%
Jinja 9 9.7%
React 8 8.6%
Twirl 7 7.5%
Mustache 4 4.3%
Handlebars 4 4.3%
Vue.js 3 3.2%
Thymeleaf 3 3.2%
Slim 3 3.2%
None 2 2.2%
HAML 2 2.2%
Django templates 2 2.2%
Twig 2 2.2%
PHP 2 2.2%
Jade 2 2.2%
Riot 1 1.1%
Hogan 1 1.1%
Scala 1 1.1%
Haml 1 1.1%
Blade 1 1.1%
Don't know 1 1.1%
Marko 1 1.1%
Freemarker 1 1.1%
JSP 1 1.1%
Razor 1 1.1%

Question 5: What CSS pre-processor do you use on this project?

Answers

Name Count Percentage
Sass 58 84.1%
We don't use a pre-processor 6 8.7%
Emotion 2 2.9%
Don't know 1 1.4%
styled-components 1 1.4%
Less 1 1.4%

Question 6: Which CSS architecture do you follow?

Answers

Name Count Percentage
We don't follow a CSS architecture 31 40.8%
BEM 28 36.8%
Don't know 6 7.9%
CSS-in-JS 4 5.3%
ITCSS 3 3.9%
OOCSS 2 2.6%
SMACCS 1 1.3%
Atomic 1 1.3%

Question 7: Does your project have its own design resources?

Answers

Name Count Percentage
Yes 33 50.0%
No 29 43.9%
In development 4 6.1%

Question 8: What frontend resources from GDS does your project use?

Answers

Name Count Percentage
GOV.UK Design System (GOV.UK Frontend) 42 25.3%
GOV.UK Frontend Toolkit 31 18.7%
GOV.UK Elements 29 17.5%
GOV.UK Prototype Kit 27 16.3%
GOV.UK Template 19 11.4%
None 9 5.4%
govuk-react 3 1.8%
Planning to migrate to GOV.UK Design System (GOV.UK Frontend) 2 1.2%
HMCTS Design System (HMCTS Frontend) 1 0.6%
MOJ Pattern Library (an extension of the GOV.UK Design System) 1 0.6%
Assets Frontend 1 0.6%
Own 1 0.6%

Question 9: How are GOV.UK frontend resources integrated into your project?

Answers

Name Count Percentage
npm 25 43.1%
Manually 7 12.1%
Gulp 5 8.6%
Gem 4 6.9%
Departmental resource 4 6.9%
We don't 4 6.9%
Badly 2 3.4%
Webpack 2 3.4%
Prototype kit 2 3.4%
CDN 1 1.7%
Github 1 1.7%
Package manager 1 1.7%

Question 10: How do you keep those resources up-to-date in your project?

Answers

Name Count Percentage
npm 18 39.1%
Manually 12 26.1%
Dependency notification service 6 13.0%
Trying our best 4 8.7%
Github 2 4.3%
We don't 2 4.3%
RSS 1 2.2%
When things break 1 2.2%

Question 11: Are there any specific improvements you'd like to see in the frontend resources offered by GDS?

Answers

  • better documentation
  • ruby gems
  • more templating languages
  • Content Delivery Network (CDN) for assets
  • simpler tools for less technical people
  • adopt a form builder
  • less reliance on polyfills
  • dont use BEM
  • tools to help port GOV.UK Frontend
  • use nunjucks extensions
  • authoring CSS rather than having to write more HTML
  • a single package and site
  • better code
  • a clear contribution model
  • accessibility
  • better support
  • versioned components
  • compiled assets including CSS
  • better JavaScript