Chris Hill-Scott 243fdb0260 Assign email branding based on user’s email domain ...

When a user creates a service we can take a pretty good guess at what
organisation they’re from.

For many organisations, especially local councils, GOV.UK branding is
not appropriate for their service. But right now every service:
- gets created with GOV.UK branding
- has to ask us to change it, even if they’ve already done so for other
  services they run

This commit starts using the `domain` field on the email branding table
to lookup what email branding to assign to a service automatically,
where we’re sure there’s a sensible default.

2018-09-05 10:32:44 +01:00

..

assets

Merge pull request #2262 from alphagov/remove_branding_type_from_set_email_branding_page

2018-08-31 13:56:44 +01:00

main

Assign email branding based on user’s email domain

2018-09-05 10:32:44 +01:00

notify_client

Assign email branding based on user’s email domain

2018-09-05 10:32:44 +01:00

status

…

templates

Merge pull request #2268 from alphagov/request-to-go-live-better-data

2018-09-04 16:25:59 +01:00

__init__.py

…

.gitignore

…

asset_fingerprinter.py

…

cloudfoundry_config.py

…

commands.py

…

config.py

Merge pull request #2268 from alphagov/request-to-go-live-better-data

2018-09-04 16:25:59 +01:00

domains.yml

Alias Barking and Dagenham council’s domain

2018-08-28 09:47:24 +01:00

email_domains.yml

…

event_handlers.py

…

navigation.py

Merge pull request #2261 from alphagov/robots.txt

2018-08-29 16:04:26 +01:00

proxy_fix.py

…

statistics_utils.py

…

template_previews.py

…

utils.py

Add canonical domain info to agreement class

2018-09-05 10:32:43 +01:00

version.py.dist

…