Home
WDS Simple Page Builder was developed with one main underlying idea: that content editors (the people choosing the layout of a page) should not be required to know HTML or CSS. This is an important distinction and it informs all the development decisions of the plugin.
What this means is that the plugin assumes that you are a theme developer, you are building a custom theme, and your theme has template parts that can be dropped into theme template files wherever you want. How and where (e.g. inside the Loop vs. outside the Loop) is up to you, but there are guidelines and best practices that will be outlined in this wiki.
As a content editor, all I need to know is that there are these things (template parts) that I can put into my post or page and I can order them however I want, and, magically, stuff happens on the front end.
From a developer perspective, we need to be more aware of that "magic" that goes into these template parts in terms of how they are built and how they interact with the theme template files.
Building Template Parts for Page Builder
WDS Simple Page Builder adds functionality that can be used much like a standard get_template_part function in WordPress. Where it performs better than get_template_part is in the fact that you (or your content editors) have the ability to customize not only which template parts are included in a page layout, but in what order they appear. There are three ways that layouts can be built for posts and pages: individually (per post/page), globally (default for all posts/pages) and through saved layouts. Additionally there are some initial options that you'll want to check out and determine if they work for your setup.