Theme Toolkit

Building blocks to develop a config-based WordPress theme., _(*1)

When building a theme, wouldn't it be nice to separate out the implementation-specific config, from the reusable logic? This is the premise upon which the Using a Config to Write Reusable Code series articles are written, and which this package enables., _(*2)

It uses the BrightNucleus\Config package for managing the configuration objects, while the classes in this package consumes them to provide an easy way to:, _(*3)

Register and enqueue Google Fonts.
Add and remove image sizes.
Unset (inherited) page templates.
Add theme support.
Register and unregister widget areas (sidebars).
Register and unregister widgets.
Manage script and style dependencies.

Installation

Requires PHP 7.1., _(*4)

In a terminal, browse to the directory with your theme in and then:, _(*5)

composer require gamajo/theme-toolkit

You can then autoload (PSR-4) or require the files as needed., _(*6)

Usage

See the example-config.php. This would typically live in your theme, at config/defaults.php., _(*7)

Your theme would then contain a function, in the functions.php, to pull in this config, and load up the individual components, which are referred to as bricks:, _(*8)

// functions.php

namespace Gamajo\ExampleTheme;

use BrightNucleus\Config\ConfigFactory;
use Gamajo\ThemeToolkit\Dependencies;
use Gamajo\ThemeToolkit\GoogleFonts;
use Gamajo\ThemeToolkit\ImageSizes;
use Gamajo\ThemeToolkit\Templates;
use Gamajo\ThemeToolkit\ThemeSupport;
use Gamajo\ThemeToolkit\Widgets;
use Gamajo\ThemeToolkit\WidgetAreas;
use Gamajo\ThemeToolkit\ThemeToolkit;

defined( 'ABSPATH' ) || exit;

if ( file_exists( __DIR__ . '/vendor/autoload.php' ) ) {
    require __DIR__ . '/vendor/autoload.php';
}


add_action( 'after_setup_theme', __NAMESPACE__ . '\setup' );
/**
 * Theme setup.
 *
 * Compose the theme toolkit bricks.
 */
function setup() {
    $config_file = __DIR__ . '/config/defaults.php';
    $config = ConfigFactory::createSubConfig( $config_file, 'Gamajo\ExampleTheme' );

    // These bricks are run in admin and front-end.
    $bricks = [
        Dependencies::class,
        ImageSizes::class,
        Templates::class,
        ThemeSupport::class,
        Widgets::class,
        WidgetAreas::class,
    ];

    // Apply logic in bricks, with configuration defined in config/defaults.php.
    ThemeToolkit::applyBricks($config, ...$bricks);


    if ( ! is_admin() ) {
        // Only front-end bricks.
        $bricks = [
            GoogleFonts::class,
        ];

        ThemeToolkit::applyBricks($config, ...$bricks);

    }
}

The 'Gamajo\ExampleTheme' string matches the two keys in the return at the bottom of the config file. Change this in the config and the function to be your company name and theme name., _(*9)

You don't have to use all of the bricks in this package; pick and choose., _(*10)

You can add your own bricks to your theme (in your src/ or similar directory), and then make use of them in the function above., _(*11)

For Genesis Framework users, see the Genesis Theme Toolkit which has extra bricks for registering layouts, breadcrumbs args etc., _(*12)