<p>Unlike some other CMS systems, Craft doesn't specify what your front-end templates should look like in any way (you could output your content as .txt files if you wanted to). It also doesn't add anything to your rendered page output that you didn't specify (with the exception of error info if 'devMode' is set to true). The default templates are really just there as placeholders so that you can confirm the system is working properly.</p>

<p>I can't say specifically what is causing your rendering/margin issue, but I would just ignore it and start with your own clean templates. All of the browsers that you mention also have some form of web inspector/development tools. If you really want to know you can 'inspect element' with the browser tools and see what css if any is causing the problem.</p>

CC BY-SA 3.0
2015-10-20T23:50:31.120Z
2015-10-20T23:50:31.120Z
Douglas McDonald
<p>Resolved by nuke and reinstall.</p>

<p>Thanks for the answers. It was in my own templates that I noticed the issue to start with. I removed all CSS to make sure it was not the cause in some odd way. I wanted to use the default template to be sure I had stock html from the system to also cut out any possible html code issues I might have mistakenly added or modified. None of my solutions worked, so I opened a ticket with Support. Brad did verify that he was able to install from scratch, remove the css, and verified it in Chrome.</p>

<p>I saved my templates that I personally created, as well the foundation.zurb components that I introduced. I deleted craft and the db, and started it over from scratch.  Once I had it back on fresh, I removed the CSS again from the stock template and the space issue was gone. </p>

<p>I re-implementable my template and foundation.zurb components again, and everything was fine this time. All of my own additions were okay as well. Something somewhere crept in on my first install somehow I guess.  Glad that it's resolved now. </p>

<p>It was odd though because I did refer back to a stock template saved from the default unzip as well as removing all CSS. I did have some posts that I added to the news feed back though so I am wondering if perhaps it crept in that way. Maybe something I did on one of the posts, because it was only ever on the news feed page that this issue appeared. </p>

<p>Thank you.</p>

<p>Logan</p>

CC BY-SA 3.0
2015-10-26T12:37:17.833Z
2015-10-26T12:37:17.833Z
logan
<p>On the default install, taking out all css. There is an extra margin space at the top of Chrome, and IE Edge but firefox is fine. I also checked out the error 404 page, and it too is fine like the standard layout page at home. </p>

<p>However, if I click news or create a new extends sub folder, they will have an extra 26 pixels at the top. </p>

<p>I noticed this trying to have a top bar flushed to the very top. I rolled back everything to stock and used the default template, took out all CSS from it, and still notice this issue. </p>

<p>here is an image comparison of the two pages, no css using Chrome.</p>

<p><a href="https://i.sstatic.net/yBybB.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/yBybB.jpg" alt="Comparison of two pages showing the difference"></a></p>

<p>Thanks,</p>

<p>Logan.</p>

<templating><css>
Extra margin in Default System on subpages like news
# Extra margin in Default System on subpages like news

(Asked by: username_0 on 2015-10-20)

On the default install, taking out all css. There is an extra margin space at the top of Chrome, and IE Edge but firefox is fine. I also checked out the error 404 page, and it too is fine like the standard layout page at home.

However, if I click news or create a new extends sub folder, they will have an extra 26 pixels at the top.

I noticed this trying to have a top bar flushed to the very top. I rolled back everything to stock and used the default template, took out all CSS from it, and still notice this issue.

here is an image comparison of the two pages, no css using Chrome.

[![Comparison of two pages showing the difference](https://i.sstatic.net/yBybB.jpg)](https://i.sstatic.net/yBybB.jpg)

Thanks,

Logan.

**Tags:** templating, css

---

## 2 answers

### Answer by username_1 on 2015-10-20. Score: 3

Unlike some other CMS systems, Craft doesn't specify what your front-end templates should look like in any way (you could output your content as .txt files if you wanted to). It also doesn't add anything to your rendered page output that you didn't specify (with the exception of error info if 'devMode' is set to true). The default templates are really just there as placeholders so that you can confirm the system is working properly.

I can't say specifically what is causing your rendering/margin issue, but I would just ignore it and start with your own clean templates. All of the browsers that you mention also have some form of web inspector/development tools. If you really want to know you can 'inspect element' with the browser tools and see what css if any is causing the problem.


---

### Answer by username_0 on 2015-10-26. Score: 1

Resolved by nuke and reinstall.

Thanks for the answers. It was in my own templates that I noticed the issue to start with. I removed all CSS to make sure it was not the cause in some odd way. I wanted to use the default template to be sure I had stock html from the system to also cut out any possible html code issues I might have mistakenly added or modified. None of my solutions worked, so I opened a ticket with Support. Brad did verify that he was able to install from scratch, remove the css, and verified it in Chrome.

I saved my templates that I personally created, as well the foundation.zurb components that I introduced. I deleted craft and the db, and started it over from scratch. Once I had it back on fresh, I removed the CSS again from the stock template and the space issue was gone.

I re-implementable my template and foundation.zurb components again, and everything was fine this time. All of my own additions were okay as well. Something somewhere crept in on my first install somehow I guess. Glad that it's resolved now.

It was odd though because I did refer back to a stock template saved from the default unzip as well as removing all CSS. I did have some posts that I added to the news feed back though so I am wondering if perhaps it crept in that way. Maybe something I did on one of the posts, because it was only ever on the news feed page that this issue appeared.

Thank you.

Logan


---

