Purchase Theme

It’s important to have a good foundation

This theme is built to be modified by a developer. Below is what you should know about this theme, so you can get the most out of it. Ideally, we recommend using this a parent theme and building all your customization in the child theme. This will enable you to receive updates that are made to the parent theme.

We’ve used all of our favorite languages, tools, and services. Producing our best version of a base theme. It is exciting to be able to share it with others. We hope you enjoy it and find it well put together.

Foundational Elements

WordPress 5.0

WordPress Version 5.0 was released to the public on December 6, 2018 . It is revolutionizing content editing with introduction of a new block editor.

Learn More

Bootstrap 4

The world’s most popular framework for building responsive and mobile-first websites.

Learn More

Sass

Sass is the most mature, stable, and powerful professional grade CSS extension language in the world.

Learn More

Advance Custom Fields Pro

Our custom built blocks are powered by ACF PRO. Developers can build their own custom blocks in the child theme.

Learn More

Font Love

Google Fonts

Google Fonts offers a large library of license free web fonts. LaLa Theme 4.0 .css and functions.php files is wired up for Google Fonts. Just edit the child theme to modify the fonts selection.

Learn More

Font Awesome 5

Developers love Font Awesome and with good reason. Their icon library offers thousands of vector icons. This theme is pre-wired for the pro license, just add in your kit number into the WordPress Options. No coding needed.

Font Awesome

More Dev Notes

Partial Templating and Inheritance

1. Partial Views

  • LLT4 uses template partials to build a full, rendered view
  • Partial views are all contained in the /resources/views folder
  • The parent and child theme each have their own set of asset bundles
    • “Assets” are files that have to be enqueued, such as stylesheets and scripts
  • Partials can be overwritten in the child by mimicking the partial path
    • E.g., the {child_dir}/.../header/banner.php will be used instead of the {parent_dir}/.../header/banner.php if the file exists
  • The ll4_view() function can be used to call in partial views with the inheritance logic already baked in

2. Stylesheets

  • While the styles contained in /resources/(sass|stylus|css) share a similar structure to views, it is only for organizational purposes
    • Child theme styles files will not overwrite parent files (since they use different asset bundles)
  • In addition, the /resources/img files are the source for any theme images, but are used mostly for background images and other CSS-releated needs

3. Scripts

  • Scripts are split up by functionality with each folder representing an enclosed function
    • E.g., “Smooth Scroll” and “Google Map” functions are all contained in their own directories
  • Different scripts are explicitly called in by the /resources/js/app.js file