How to Configure Jetpack for Layers
JetPack is an amazing plugin from Automattic, the creators of WordPress.com and members of the WordPress core team. It packs a ton of WordPress-essential added functionality into one pluginthat is beneficial to most sites. Not all of this functionality is necessary for your site though, and some of it can conflict with or override functionality already present in Layers. This doc aims to help you configure JetPack for a Layers site to get the best out of performance and avoid ambiguous problems.
Check Enabled Settings
JetPack will enable a handful of settings by default when you activate it, most of which are safe. Once you connect to your WordPress.com account, it will also prompt you to activate the rest. If you have yet to activate these enhanced options, don’t.
Go to→ to check enabled features.
To deactivate a feature, hover over it and click Deactivate
We recommend the following be deactivated (or left not activated)
This feature is redundant to the CSS panel already available in the Customizer or to DevKit, if installed. While it does not directly conflict with Layers, it can be confusing for your client or site owner and we often find custom css stored in Jetpack by accident or that gets forgotten, leaving you wondering why things don’t look right.
Unless you have a child theme that specifically includes support for Jetpack Infinite Scroll, this feature should be left disabled as it can conflict with the Masonry option on Layers widgets.
This does not need to be active unless your site specifically needs it.
This should be left deactivated unless you specifically want to use markdown to format your posts. Markdown can lead to unexpected results from using quotes or asterisks in posts.
Layers and Layers child themes are responsive, making the mobile theme unnecessary. Only activate it if you specifically want the Jetpack mobile look to take over your main site on mobile devices.
Only activate if you specifically need this service and are not running an SSL protected website. Photon can also cause image sizing issues in widgets due to offsite hosted images not being processed by the theme’s sizing functions.