Title: Gap between header and container
Last modified: September 26, 2020

---

# Gap between header and container

 *  Resolved [rob33](https://wordpress.org/support/users/rob33/)
 * (@rob33)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/)
 * My bad on this and probably straight forward but removing gap between header 
   and container on homepage – i.e the gap between the header and the screen slider
   which sits at the top of container obviously therefore brings each page and post
   flush with header. Is there a way to bring homepage up but not pages and posts
   and wc product pages in this case.
 * Tried separate or one container.
 * Thanks,
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fgap-between-header-and-container%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Tom](https://wordpress.org/support/users/edge22/)
 * (@edge22)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13458426)
 * Ideally what I would do is use the full-width or contained option in GeneratePress:
   [https://docs.generatepress.com/article/page-builder-container/](https://docs.generatepress.com/article/page-builder-container/)
 * However, if you use the full-width option, you will then need to make your individual
   sections on the page contained.
 * Otherwise you can target individual pages and remove the margin:
 *     ```
       .page-id-1514.separate-containers .site-main {
           margin-top: 0;
       }
       ```
   
 *  Thread Starter [rob33](https://wordpress.org/support/users/rob33/)
 * (@rob33)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13459298)
 * That worked a treat – as always, many thanks Tom.
 *  Plugin Author [Tom](https://wordpress.org/support/users/edge22/)
 * (@edge22)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13460990)
 * Glad I could help! 🙂
 *  Thread Starter [rob33](https://wordpress.org/support/users/rob33/)
 * (@rob33)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13486860)
 * Ahhh – just a quickie – the gap remains on the mobile. Would it be possible to
   amend the css so it includes removing both on mobile and tablet s’il vous plait.
 *  Plugin Author [Tom](https://wordpress.org/support/users/edge22/)
 * (@edge22)
 * [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13488147)
 * Ah, that’s the content padding.
 * The full width content option I mentioned previously would take care of this 
   as well, but there is CSS you can use:
 *     ```
       @media (max-width: 768px) {
           .page-id-1514.separate-containers .inside-article {
               padding-top: 0;
           }
       }
       ```
   
 * Targeting the one page like this will CSS is fine, but if you find yourself needing
   to add more pages, I would suggest looking at the page builder container option
   🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Gap between header and container’ is closed to new replies.

 * ![](https://ps.w.org/generateblocks/assets/icon.svg?rev=3239461)
 * [GenerateBlocks](https://wordpress.org/plugins/generateblocks/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/generateblocks/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/generateblocks/)
 * [Active Topics](https://wordpress.org/support/plugin/generateblocks/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/generateblocks/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/generateblocks/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Tom](https://wordpress.org/support/users/edge22/)
 * Last activity: [5 years, 7 months ago](https://wordpress.org/support/topic/gap-between-header-and-container/#post-13488147)
 * Status: resolved