Juniper - WordPress starter boilerplate + theme

Overview

Juniper is built on top of the Bedrock boilerplate.

Bedrock is a modern WordPress stack that helps you get started with the best development tools and project structure. The theme is a native WordPress block theme (Full Site Editing templates/parts) combined with native ACF Blocks (PHP render.php templates, no templating engine in between).

Features

• Easy WordPress configuration with environment specific files
• File structure which makes keeping and maintaining your project on a Git a lot easier
• Dependency management with Composer
• Native WordPress block theme (FSE templates/parts) + native ACF Blocks
• Bash console scripts to make creating project from the scratch much easier

Requirements

• PHP >= 8.1
• Composer - Install
• PHPCS & PHPCBF with WordPress-Extra standard installed

Installation

1. Create local database as you would do for normal WP instance
2. Map project main catalogue to domain on your localhost
3. Start a new project:

   $ bash start.sh

   and follow the instructions in the console. Type in details from step 1 and 2. .env file will be crated for you (all DB and site details sits there)
4. Fill correct domain details in .htaccess in main catalogue.
5. Check if /web/ directory has .htaccess file with default WP entries.
6. Run

   $ bash work.sh

   in main project directory
7. Start coding your theme in /web/app/themes/juniper-theme/ :)

Composer dependencies

To maintain project correctly we insist you to use composer.json in main catalogue.

If you want to add new plugin to your project you can use WPackagist - the only thing you need is plugin slug from the main WP repository.

You can update them with the same easy way by changing version in composer.json.

Bash scripts

The main operations that we automate have been handled by below scripts: :

1. start.sh - used for the initial configuration of the project. Through this process, we areable to enter the basic data to the database, define the main URL and ACF key. After providing those information, the installer will generate an .env file, which in our case will contain all configuration data (as in wp-config.php in a vanilla WordPress installation).

2. work.sh - used every time you work on a project. It compiles the styles in real time by calling a parcel script to listen for file changes.

WP-CLI Commands

1. Adding Custom Post Types - After getting the name, a CPT will be created. Its editing will of course be possible later, because this command will generate a file in the theme directory.

$ wp add cpt --name="Product"

2. Adding Taxonomies - Add a name of the taxonomy you want and the slug name of the posts you want it to be attached to and this command will take care of the rest

$ wp add taxonomy --name="Category" --post="product"

3. Adding Gutenberg Blocks - This scaffolds a native ACF block (registered via acf_register_block_type()) with a plain PHP render.php template. Keywords and description fields are optional

$ wp add block --name="Reviews" --keywords="quote,stars" --description="Show three newest reviews"