app/assets/stylesheets/_grids.scss

.column-three-quarters {
  @include grid-column(3/4);
}

.column-one-eighth {
  @include grid-column(1/8);
}

.column-seven-eighths {
  @include grid-column(7/8);
}

.bottom-gutter {
  margin-bottom: $gutter;
  clear: both;
}

.bottom-gutter-2-3 {
  margin-bottom: $gutter * 2/3;
}

.align-with-heading {
  display: block;
  text-align: center;
  margin-top: 45px;
  padding-left: 2px;
  padding-right: 2px;
}
Make navigation column 1/4 width 2015-12-17 10:18:31 +00:00			`.column-three-quarters {`
			`@include grid-column(3/4);`
			`}`
Page for adding a new service This page is exactly the same as the page for adding your first service, save the heading text. So all this commit does is: - set up two routes (`/add-service`, `/add-service/first`) for each of the two journeys and change the existing journeys to use the `/add-service/first` route - add logic to show different heading text depending on the journey - add a link to the new (`/add-service`) route in the service chooser dropdown 2016-01-18 10:47:53 +00:00
Preview service name when adding a new service This commit adds a new page, which appears after a user enters the name for their new service. It shows how the service name will appear in emails and text messages. This means that the new service is not created until after they have confirmed that the name is appropriate in context. This has also involved: - visual changes to the ‘email template’ pattern, which wasn’t very refined before - removing a bunch of words from the enter service name page, because most users don’t read them, and we reckon that showing a preview is a better way of getting them to understand what is meant by service name Still to do: - validating the the generated email address for a service is unique (on the API) side - having the API return the generated email address, rather than determining it in the admin app 2016-02-18 14:54:59 +00:00			`.column-one-eighth {`
			`@include grid-column(1/8);`
			`}`

			`.column-seven-eighths {`
			`@include grid-column(7/8);`
			`}`

Page for adding a new service This page is exactly the same as the page for adding your first service, save the heading text. So all this commit does is: - set up two routes (`/add-service`, `/add-service/first`) for each of the two journeys and change the existing journeys to use the `/add-service/first` route - add logic to show different heading text depending on the journey - add a link to the new (`/add-service`) route in the service chooser dropdown 2016-01-18 10:47:53 +00:00			`.bottom-gutter {`
			`margin-bottom: $gutter;`
Preview service name when adding a new service This commit adds a new page, which appears after a user enters the name for their new service. It shows how the service name will appear in emails and text messages. This means that the new service is not created until after they have confirmed that the name is appropriate in context. This has also involved: - visual changes to the ‘email template’ pattern, which wasn’t very refined before - removing a bunch of words from the enter service name page, because most users don’t read them, and we reckon that showing a preview is a better way of getting them to understand what is meant by service name Still to do: - validating the the generated email address for a service is unique (on the API) side - having the API return the generated email address, rather than determining it in the admin app 2016-02-18 14:54:59 +00:00			`clear: both;`
Page for adding a new service This page is exactly the same as the page for adding your first service, save the heading text. So all this commit does is: - set up two routes (`/add-service`, `/add-service/first`) for each of the two journeys and change the existing journeys to use the `/add-service/first` route - add logic to show different heading text depending on the journey - add a link to the new (`/add-service`) route in the service chooser dropdown 2016-01-18 10:47:53 +00:00			`}`
Give users better guidance about CSV files This commit adds some guidance on the ‘Add recipients’ page about what should be in the CSV file. The guidance is contextual to the template, and based on the problems that we saw users having yesterday. 2016-02-26 16:22:07 +00:00
			`.bottom-gutter-2-3 {`
			`margin-bottom: $gutter * 2/3;`
			`}`
Move ‘new thing’ buttons alongside heading On the send messages and manage team pages we have big green buttons for adding/inviting a new template or team member. On the add template page it was at the bottom, and often got missed. On the manage team page it was at the top, but maybe too prominent because it’s big and green. This commit tries putting it in the top right of the page instead (except when the template page is empty, in which case it’s unchanged). 2016-03-11 07:47:46 +00:00
			`.align-with-heading {`
			`display: block;`
			`text-align: center;`
			`margin-top: 45px;`
			`padding-left: 2px;`
			`padding-right: 2px;`
			`}`