This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

Layouts vs Templates

  • Creator
  • #839

    Apologies upfront for my cluelessness… still coming to grips with WordPress terminology and application after years of static HTML and CSS thinking.

    I have a number of pages that I’d like to share a common appearance (for example: top slider, slogan, 4 columns below). If I use the layout builder to create a new layout (e.g., “Products”) it looks like I have to also populate that layout with unique content. If so, does this mean that I’d need to create 4 different layouts (Product-1, Product-2, etc.) for 4 different product pages or can I apply one “unpopulated” layout to several pre-existing pages that already have content and retain that content on those pages?

    Can the content of the pages that have custom layouts applied be edited from within the page or do I have to go back to its layout and edit its content there?

    I guess what I’m looking for is the equivalent of a Dreamweaver template but the only Jump Start template that seems appropriate is “Custom”…. which gets me back to the layout issues.

    I hoped that I’ve explained my problem clearly enough and that you’ll be able to help.


Viewing 2 replies - 1 through 2 (of 2 total)
  • Author
  • #845
    Jason Bobich


    So keep in mind that the framework’s custom layouts and WordPress’s “Page Templates” are two separate things. A WordPress page template is where you’d actually create a physical, coded template file that you could then attach to your pages. —

    Within our framework, a “custom layout” is something that is intended to be applied to one individual page, opposed to a re-usable template. When you create a custom layout, you cannot use them on multiple pages that have different content populating various elements of that layout.

    So, in a nutshell, 1 custom layout = 1 page. In your case, you’d have to create a unique custom layout and page for each product if you’re using the Layout Builder plugin.

    However, I do understand the confusion with some of the concepts. When I originally designed the layout builder, it was meant to be used for that one special page on your site like the homepage. So, if you’re using to create many pages, it can be a little confusing jumping back and forth between the Builder and editing your pages, and things seem sort of disjointed.

    Over the last week, we’ve been working on some improvements to this and you should see some updates very soon to Jump Start and the Layout Builder plugin that will make editing these things much easier to manage.

    1) You will now be able to start a new layout, using a pre-existing layout as the starting point.

    2) You wil now be able to manage the custom layout applied to a page directly from the Edit Page screen.

    3) There will be a new “Simple Slider” element added to the Layout Builder’s elements that will allow you to create a quick, basic slider directly in the Builder or Edit Page screen without having to create anything under the Slider Manager plugin.


    We’ve got #1 and #2 finished, but will now be working on #3 to finish that before pushing out v1.1 of the Layout Builder.

    While the internal setup will not change, hopefully the continuity of editing these items in relation to their pages will. So if you do decide to create custom layouts for each product, you can feel free to do this, and later when you update to our new version of the Layout Builder, everything will remain in place.


    Jason –

    Thanks so much for the clarifications! I guess that I though the layout builder was more of a template creation tool but in the case of the site I’m now building, the 1 custom layout = 1 page constraint won’t be a big issue. I was more concerned about when I pass off the job to the client and imagining their confusion when I tried to explain that the page content isn’t editable on the page, but instead on the page layout. Looks like the changes you’ve got coming up in 1.1 should reduce or eliminate that issue.

    Thanks too for your terrific customer support… truly exceptional!

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.