app/templates/withoutnav_template.html

{% extends "admin_template.html" %}

{% block fullwidth_content %}
  <div id="content">
    <main role="main">
      {% include 'flash_messages.html' %}
      {% block maincolumn_content %}{% endblock %}
    </main>
  </div>
{% endblock %}
Make spacing and position of banners consistent Banners should always be the first thing on the page. Because headers already have padding we don’t want to put padding on the container. So banners should also have top padding to distance then from the red bar. They should also sit in the 3/4 column if the page has side navigation. This commit adds a new template (`withoutnav_template.html`) which extends `admin_template.html`. All views then extend one or the other, never the `admin_template.html` directly. This means that `admin_template.html` doesn’t have to make decisions about where the flash messages are displayed. 2016-02-01 12:15:38 +00:00			`{% extends "admin_template.html" %}`

			`{% block fullwidth_content %}`
Make a full width base template We need this because the top section of the new product page will be going full-bleed. 2016-11-22 17:15:31 +00:00			`<div id="content">`
			`<main role="main">`
			`{% include 'flash_messages.html' %}`
			`{% block maincolumn_content %}{% endblock %}`
			`</main>`
			`</div>`
Make spacing and position of banners consistent Banners should always be the first thing on the page. Because headers already have padding we don’t want to put padding on the container. So banners should also have top padding to distance then from the red bar. They should also sit in the 3/4 column if the page has side navigation. This commit adds a new template (`withoutnav_template.html`) which extends `admin_template.html`. All views then extend one or the other, never the `admin_template.html` directly. This means that `admin_template.html` doesn’t have to make decisions about where the flash messages are displayed. 2016-02-01 12:15:38 +00:00			`{% endblock %}`