Starter sites and the section library

What this does

DJIA Builder → Starter sites shows the bundled packs; step 4 of the Get started screen links to the same screens. Choosing a pack opens its dry run: the list of everything the import would create, with your options applied. Nothing is written until you click the import button. Every object an import creates carries the id of that import, which is how Undo finds it again. Documents go through the editor's own validation, and nothing in a pack runs as code. Both screens need the manage_options capability.

The three starter sites

Steps

1. Open a pack.

   On DJIA Builder → Starter sites, each card shows previews, what the pack contains and the plugins it needs ("Uses WooCommerce (active)", "Needs WooCommerce (not installed)"). Click Preview import.

2. Set the options.

   Import as: Published ("The demo goes live right away.") or Drafts ("Nothing changes for visitors until you publish."). Global styles: "Use the demo’s styles" (the default), "Add the demo’s styles to mine" or "Keep my styles"; your breakpoints are kept in every case. Two checkboxes, both on by default: "Use its home and blog pages in Settings → Reading (published imports only)" and "Imported templates take priority over my published templates". Click Update dry run after a change.

3. Read the dry run.

   The panel "What the import does" shows Ready to import or Blocked, counts per type and, unless you keep your styles, how many variables and classes are new or changed. "Everything it creates" lists each item as New, Existing (a category or tag you already have is reused) or Skipped, with notes such as an address that is taken (WordPress adds a number) or "your published … of this type stays; the imported one takes priority".

4. Import.

   Click Import Studio (or Esenca, Journal). A published import publishes all its documents and the global styles together, in one release.

5. Look at it.

   The import appears under "Imported starter sites" with its id, time and status; View site opens the home page. The documents are in the Templates, Layouts and Components lists like your own.

The same works from WP-CLI. import needs an administrator; its flags mirror the options (--status, --globals, --no-front-page, --no-priority).

wp djb starter list
# dry run, as text or --format=json
wp djb starter plan journal --status=draft --globals=keep
wp djb starter import journal --status=draft --globals=keep --user=admin
wp djb starter imports
wp djb starter undo <import-id> --user=admin

Undo an import

Click Undo import in the "Imported starter sites" table and confirm "Delete everything this import created and restore your previous global styles?". DJIA Builder permanently deletes every page, post, product, image, menu, category and tag that carries this import's id, which takes the imported templates, layouts and components out of the live release. It then restores the front page and posts page settings and your previous global styles; after a published import it publishes the styles visitors had before.

The section library

DJIA Builder → Sections holds 14 "whole pieces of a page, ready to use", grouped by category: two heroes (centred, picture beside the words), two feature blocks, pricing with three plans, an FAQ, four counters, three testimonials, a team of four, a moving logo strip, a timeline, a before / after comparison, a contact block and a call-to-action banner. Add to my components imports the section as a published component and says "… was added to your components. Open a page in the editor and drop it in, or open it under Components to change the words first." Each click adds a new copy; the card counts them ("Added 2 times").

A section brings no global styles or classes of its own and never touches yours. Every length in it is a token with a fallback value, so it looks right before you define those tokens. Insert it with the Component element, as described in Components.

Limits

• Undo deletes content edited since the import, permanently; it does not go to the trash.
• A published import needs the runtime. Without it the dry run is blocked: "The runtime is not available, so nothing can be published. Import as drafts or repair DJIA Builder on the Dashboard."
• A draft import changes nothing for visitors "until you publish the pages, templates and global styles in the editor".
• An address that is already taken gets a number from WordPress, and a menu whose name exists is created again with a number.
• Esenca cannot be imported without an active WooCommerce.

If it doesn't work

• "WooCommerce is not installed." or "… is installed but not active." Use the Install WooCommerce or Activate WooCommerce button in the dry run, then update the dry run.
• The Studio contact page has an e-mail button instead of a form. The dry run warned: without Fluent Forms, or a form in it, the page is imported without the form and the pack puts the button in its place. Create a Fluent Forms form, undo and import again.
• Your own templates still win. You turned off "Imported templates take priority over my published templates". Raise the imported templates' priority in the editor, or undo and import again with the option on.
• Undo reports that the previous global styles could not be restored. The imported content is removed already; only the styles failed. Set them back in Site settings and publish them.

Last verified 2026-10-20 · tested with DJIA Builder 1.0.20.15
To confirm Verified against the plugin code; run the steps on a test site before launch