Step 4: Custom Header

Written by the Divi Engine Documentation Team

Watch This Video

Introduction

Follow this information to use the Custom Header of Divi Mobile.

Read First

As you build your mobile menu you need to know two things.  Firstly, due to the way WordPress has been built, there may be times that the live preview mode does not load instantly. If you find this happening, please publish and reload until you see your work. Note that you may also have to view your mobile menu from a device that is not logged into the wp-admin dashboard of your Divi website such as your mobile phone. Secondly, Divi Mobile saves the menu you build to your active theme. Therefore if you change your active theme to a new child or parent theme then you will need to rebuild your menu.

Go To The Theme Customizer

Make your way to the Divi customizer by clicking on Appearance > Customize.

Click On Divi Mobile Custom Header

Click on Divi Mobile and then on Custom Header.

Custom Header

The custom header section of Divi Mobile allows you to build a custom header. If you decide to build your own you will then be able to build it using the features we have provided. While each element is self-explanatory, we do provide information on some of the features below to assist you.

CREATE A CUSTOM HEADER

Do you want to disable the default Divi header and create your own header? If so then click YES. If you click NO, then you can build your header with the Theme Builder or by using the default Divi header.

CUSTOM HEADER LOGO

Upload your logo here.

FIXED MENU ON SCROLL

Click YES if you want your custom menu to be stuck to the top of your browser.

LOGO POSITION

Do you want your logo to be in the centre, the left or the right?

CART ICON

Remove the cart icon, colour it or change its size.

SEARCH ICON

Style the search icon.

More Support?

Please email us at [email protected] if you are unable to get Divi mobile working.

Next Step

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.