2015-11-25 16:21:28 +00:00
|
|
|
|
{% extends "govuk_template.html" %}
|
2016-01-27 15:22:47 +00:00
|
|
|
|
{% from "components/banner.html" import banner %}
|
2015-11-25 16:21:28 +00:00
|
|
|
|
|
2015-12-10 15:57:32 +00:00
|
|
|
|
{% block head %}
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<!--[if gt IE 8]><!-->
|
2016-02-10 15:47:00 +00:00
|
|
|
|
<link rel="stylesheet" media="screen" href="{{ asset_url('stylesheets/main.css') }}" />
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<!--<![endif]-->
|
2016-02-01 14:46:12 +00:00
|
|
|
|
<style>
|
2016-07-28 09:05:28 +01:00
|
|
|
|
#global-header-bar { background-color: {{header_colour}} }
|
2016-02-01 14:46:12 +00:00
|
|
|
|
</style>
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<!--[if IE 6]>
|
2016-02-10 15:47:00 +00:00
|
|
|
|
<link rel="stylesheet" media="screen" href="{{ asset_url('stylesheets/main-ie6.css') }}" />
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<![endif]-->
|
|
|
|
|
|
<!--[if IE 7]>
|
2016-02-10 15:47:00 +00:00
|
|
|
|
<link rel="stylesheet" media="screen" href="{{ asset_url('stylesheets/main-ie7.css') }}" />
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<![endif]-->
|
|
|
|
|
|
<!--[if IE 8]>
|
2016-02-10 15:47:00 +00:00
|
|
|
|
<link rel="stylesheet" media="screen" href="{{ asset_url('stylesheets/main-ie8.css') }}" />
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
<![endif]-->
|
2017-10-27 11:33:10 +01:00
|
|
|
|
<meta name="google-site-verification" content="niWnSqImOWz6mVQTYqNb5tFK8HaKSB4b3ED4Z9gtUQ0" />
|
2017-11-14 17:25:32 +00:00
|
|
|
|
{% block meta %}
|
|
|
|
|
|
{% endblock %}
|
2015-12-10 15:57:32 +00:00
|
|
|
|
{% endblock %}
|
2015-12-07 16:18:05 +00:00
|
|
|
|
|
2015-11-25 16:21:28 +00:00
|
|
|
|
{% block page_title %}
|
2017-02-13 10:45:15 +00:00
|
|
|
|
{% block per_page_title %}{% endblock %} – GOV.UK Notify
|
2015-11-25 16:21:28 +00:00
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
|
|
|
|
|
{% block cookie_message %}
|
2016-03-16 11:01:19 +00:00
|
|
|
|
<p>
|
|
|
|
|
|
GOV.UK Notify uses cookies to make the site simpler.
|
|
|
|
|
|
<a href="{{ url_for("main.cookies") }}">Find out more about cookies</a>
|
|
|
|
|
|
</p>
|
2015-11-25 16:21:28 +00:00
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
2016-01-07 12:43:10 +00:00
|
|
|
|
{% block header_class %}with-proposition{% endblock %}
|
|
|
|
|
|
{% block proposition_header %}
|
|
|
|
|
|
<div class="header-proposition">
|
2016-02-01 11:26:38 +00:00
|
|
|
|
<div class="content">
|
2016-04-02 10:56:23 +01:00
|
|
|
|
<a href="#proposition-links" class="js-header-toggle menu">Menu</a>
|
|
|
|
|
|
<nav id="proposition-menu">
|
|
|
|
|
|
<ul id="proposition-links">
|
2018-04-25 11:11:37 +01:00
|
|
|
|
<li><a href="{{ url_for('main.support') }}" {{ header_navigation.is_selected('support') }}>Support</a></li>
|
2016-05-04 13:01:55 +01:00
|
|
|
|
{% if current_user.is_authenticated %}
|
2018-04-25 11:11:37 +01:00
|
|
|
|
<li><a href="{{ url_for('main.documentation') }}" {{ header_navigation.is_selected('documentation') }}>Documentation</a></li>
|
|
|
|
|
|
<li><a href="{{ url_for('main.user_profile') }}" {{ header_navigation.is_selected('user-profile') }}>{{ current_user.name }}</a></li>
|
2018-02-27 16:45:20 +00:00
|
|
|
|
{% if current_user.platform_admin %}
|
2018-04-25 11:11:37 +01:00
|
|
|
|
<li><a href="{{ url_for('main.platform_admin') }}" {{ header_navigation.is_selected('platform-admin') }}>Platform admin</a></li>
|
2016-05-24 15:52:44 +01:00
|
|
|
|
{% endif %}
|
2017-11-29 13:59:26 +00:00
|
|
|
|
<li><a href="{{ url_for('main.sign_out')}}">Sign out</a></li>
|
2016-04-02 10:56:23 +01:00
|
|
|
|
{% else %}
|
2018-04-25 11:11:37 +01:00
|
|
|
|
<li><a href="{{ url_for('main.features') }}" {{ header_navigation.is_selected('features') }}>Features</a></li>
|
|
|
|
|
|
<li><a href="{{ url_for('main.pricing' )}}" {{ header_navigation.is_selected('pricing') }}>Pricing</a></li>
|
|
|
|
|
|
<li><a href="{{ url_for('main.documentation') }}" {{ header_navigation.is_selected('documentation') }}>Documentation</a></li>
|
|
|
|
|
|
<li><a href="{{ url_for('main.sign_in' )}}" {{ header_navigation.is_selected('sign-in') }}>Sign in</a></li>
|
2016-04-02 10:56:23 +01:00
|
|
|
|
{% endif %}
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
</nav>
|
2016-01-06 16:40:38 +00:00
|
|
|
|
</div>
|
2016-01-07 12:43:10 +00:00
|
|
|
|
</div>
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
{% endblock %}
|
2015-12-03 16:01:00 +00:00
|
|
|
|
|
2016-01-07 17:13:49 +00:00
|
|
|
|
|
2016-11-18 10:54:34 +00:00
|
|
|
|
{% set global_header_text = "GOV.UK <span id='product-name'>Notify</span>"|safe %}
|
2015-11-25 16:21:28 +00:00
|
|
|
|
|
2018-03-08 16:51:53 +00:00
|
|
|
|
{% set homepage_url = url_for('main.show_accounts_or_dashboard') %}
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
|
|
|
|
|
|
{% block content %}
|
2016-11-22 17:15:31 +00:00
|
|
|
|
{% block fullwidth_content %}{% endblock %}
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
2016-03-18 16:25:43 +00:00
|
|
|
|
{% block footer_top %}
|
|
|
|
|
|
<div class="footer-categories">
|
|
|
|
|
|
<div class="footer-categories-wrapper">
|
|
|
|
|
|
<div class="grid-row">
|
2017-11-30 17:31:27 +00:00
|
|
|
|
<div class="column-one-quarter">
|
2016-03-18 16:25:43 +00:00
|
|
|
|
<ul>
|
2016-12-14 11:42:54 +00:00
|
|
|
|
<li><a href="{{ url_for('main.support') }}">Support</a></li>
|
2017-11-30 17:33:44 +00:00
|
|
|
|
<li><a href="https://status.notifications.service.gov.uk">System status</a></li>
|
2017-08-09 10:57:49 +01:00
|
|
|
|
<li><a href="https://www.gov.uk/performance/govuk-notify">Performance</a></li>
|
2017-11-30 17:34:11 +00:00
|
|
|
|
<li><a href="https://ukgovernmentdigital.slack.com/messages/govuk-notify">Slack channel</a></li>
|
2018-01-24 10:34:06 +00:00
|
|
|
|
<li><a href="https://governmentasaplatform.blog.gov.uk/category/gov-uk-notify/">Blog</a></li>
|
2016-03-18 16:25:43 +00:00
|
|
|
|
</ul>
|
|
|
|
|
|
</div>
|
2017-11-30 17:31:27 +00:00
|
|
|
|
<div class="column-one-quarter">
|
2016-03-30 15:47:00 +01:00
|
|
|
|
<ul>
|
2017-06-14 16:14:16 +01:00
|
|
|
|
<li><a href="{{ url_for("main.features") }}">Features</a></li>
|
2017-06-14 16:18:36 +01:00
|
|
|
|
<li><a href="{{ url_for("main.roadmap") }}">Roadmap</a></li>
|
2017-11-30 17:26:49 +00:00
|
|
|
|
<li><a href="{{ url_for("main.security") }}">Security</a></li>
|
2016-08-10 10:33:50 +01:00
|
|
|
|
<li><a href="{{ url_for("main.terms") }}">Terms of use</a></li>
|
2017-11-30 17:26:49 +00:00
|
|
|
|
<li><a href="{{ url_for("main.using_notify") }}">Using Notify</a></li>
|
2016-03-30 15:47:00 +01:00
|
|
|
|
</ul>
|
2016-03-18 16:25:43 +00:00
|
|
|
|
</div>
|
2017-11-30 17:31:27 +00:00
|
|
|
|
<div class="column-one-quarter">
|
|
|
|
|
|
<ul>
|
|
|
|
|
|
<li><a href="{{ url_for("main.pricing") }}">Pricing</a></li>
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
<div class="column-one-quarter">
|
2016-04-19 10:36:41 +01:00
|
|
|
|
<ul>
|
2017-11-30 17:33:44 +00:00
|
|
|
|
<li><a href="{{ url_for("main.documentation") }}">Documentation</a></li>
|
2016-04-19 10:36:41 +01:00
|
|
|
|
</ul>
|
2016-03-18 16:25:43 +00:00
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
2016-03-16 11:01:19 +00:00
|
|
|
|
{% block footer_support_links %}
|
|
|
|
|
|
<nav class="footer-nav">
|
|
|
|
|
|
Built by the <a href="https://www.gov.uk/government/organisations/government-digital-service">Government Digital Service</a>
|
2018-07-19 15:08:02 +01:00
|
|
|
|
<a href="{{ url_for("main.privacy") }}">Privacy</a>
|
2016-05-03 12:26:44 +01:00
|
|
|
|
<a href="{{ url_for("main.cookies") }}">Cookies</a>
|
2018-07-20 08:42:01 +01:00
|
|
|
|
{% if current_service and current_service.research_mode %}
|
2016-06-23 17:31:45 +01:00
|
|
|
|
<span id="research-mode" class="research-mode">research mode</span>
|
2016-06-01 16:07:43 +01:00
|
|
|
|
{% endif %}
|
2016-03-16 11:01:19 +00:00
|
|
|
|
</nav>
|
|
|
|
|
|
{% endblock %}
|
|
|
|
|
|
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
{% block body_end %}
|
2017-02-13 16:43:12 +00:00
|
|
|
|
<script type="text/javascript" src="{{ asset_url('javascripts/all.js') }}"></script>
|
2016-10-05 10:55:04 +01:00
|
|
|
|
<script>
|
|
|
|
|
|
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
|
|
|
|
|
|
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
|
|
|
|
|
|
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
|
|
|
|
|
|
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
|
|
|
|
|
|
ga('create', 'UA-75215134-1', 'auto');
|
2017-10-26 11:11:05 +01:00
|
|
|
|
ga('set', 'anonymizeIp', true);
|
|
|
|
|
|
ga('set', 'displayFeaturesTask', null);
|
|
|
|
|
|
ga('set', 'transport', 'beacon');
|
2018-08-08 08:49:16 +01:00
|
|
|
|
// strip UUIDs
|
|
|
|
|
|
page = (window.location.pathname + window.location.search).replace(
|
|
|
|
|
|
/[a-f0-9]{8}-?[a-f0-9]{4}-?4[a-f0-9]{3}-?[89ab][a-f0-9]{3}-?[a-f0-9]{12}/g, '…'
|
|
|
|
|
|
)
|
|
|
|
|
|
ga('send', 'pageview', page);
|
2016-10-05 10:55:04 +01:00
|
|
|
|
</script>
|
Use a Node-based tools for handling assets
…or how to move a bunch of things from a bunch of different places into
`app/static`.
There are three main reasons not to use Flask Assets:
- It had some strange behaviour like only
- It was based on Ruby SASS, which is slower to get new features than libsass,
and meant depending on Ruby, and having the SASS Gem globally installed—so
you’re already out of being a ‘pure’ Python app
- Martyn and I have experience of doing it this way on Marketplace, and we’ve
ironed out the initial rough patches
The specific technologies this introduces, all of which are Node-based:
- Gulp – like a Makefile written in Javascript
- NPM – package management, used for managing Gulp and its related dependencies
- Bower – also package management, and the only way I can think to have
GOV.UK template as a proper dependency
…speaking of which, GOV.UK template is now a dependency. This means it can’t be
modified at all (eg to add a global `#content` wrapper), so every page now
inherits from a template that has this wrapper. But it also means that we have a
clean upgrade path when the template is modified.
Everything else (toolkit, elements) I’ve kept as submodules but moved them to a
more logical place (`app/assets` not `app/assets/stylesheets`, because they
contain more than just SASS/CSS).
2015-12-15 08:20:25 +00:00
|
|
|
|
{% endblock %}
|