# Sage first-timer queries: inserting image assets into templates and issues with page-header.php

**URL:** https://discourse.roots.io/t/sage-first-timer-queries-inserting-image-assets-into-templates-and-issues-with-page-header-php/4833
**Category:** sage
**Created:** 2015-09-25T11:50:38Z
**Posts:** 9
**Showing post:** 7 of 9

## Post 7 by @kalenjohnson — 2015-09-25T16:17:51Z

> [@rwintle](#):
>
> Also, just wondering if you guys have ever discussed (perhaps on Roots Radio) the decisions you made in base.php? I just had to strip out some stuff from there because I wanted a full-width (Bootstrap: container-fluid) component in a template, and now I’ve got a load of repetition again.

What are you having to repeat a lot? If it’s just a `.container` class, I wouldn’t say that’s a horrible thing… that’s basically regualr Bootstrap markup and if you’re going full-width, you’re going to have to have a full-width container, generally `.container-fluid` with some other type of identifier, as you’ll most likely want to give it a specific background color or image. Then to contain the content by default really, you do have to add a `.container` eventually.

The workaround to this is keeping the `.container` class where it is and making use of `calc()` and `vw`, as Austin shows here: [Base wrapper with fullwidth elements and sidebar with DRY - #2 by austin](https://discourse.roots.io/t/base-wrapper-with-fullwidth-elements-and-sidebar-with-dry/4641/2)

But even then, you’ll still most likely want to have a `.container` on the inner content.

---

_[View the full topic](https://discourse.roots.io/t/sage-first-timer-queries-inserting-image-assets-into-templates-and-issues-with-page-header-php/4833)._