You know the drill:

You make yourself a coffee in the morning and sit down to set up a project for a custom WordPress website, and in no time it’s already dark outside the window. This is why we have created Juniper. We wanted to save those 8 hours of work each time we started a new custom project on WordPress. Now you can take the best in class frameworks we prepared for you and focus on what really matters!

Juniper is a starter boilerplate built on top of Bedrock which makes WordPress work more convenient by letting you separate the frontend layer from the backend in a simplified way.

Juniper uses Timber to render the theme. This approach allows you to power your WordPress website with Twig template engine to help organize logic and frontend part separately. With this approach you easily avoid a headache which was caused by the cumbersome, large .php files with mixed UI and business logic. Put the visual part in .twig files, backend layer in .php and make your work more organized with Juniper!

All of the WordPress experts working in large teams face the problem of code consistency across different local environments of developers engaged in the project. Here comes Juniper with a composer packages management system. From now on versions of the plugins, WordPress and all external resources can be maintained with ease. When utilizing such a stack, we found out that a major part of the actions, such as initializing a project or creating supplemental posts/taxonomies, can be automated.

That’s when the conception of creating the origin of the Juniper command line was born. In the currently published version, it is a set of files with the .sh extension, which abbreviates the time of creating custom blocks and functionalities required while building the project.

Juniper is a boilerplate that aims to bring an object-oriented approach to the theme. Therefore, most of the functionalities generated by the above scripts are object-oriented. We encourage you to familiarize yourself with the structure of files in the inc directory of the theme folder.

A preview Cypress script has additionally been integrated to the current version which checks whether the endpoint concerning the global visibility of users is blocked on the portal.

During the development of the Juniper, we endeavored to adhere to the WordPress-Extra standards, which we also encourage future users to do. To make it easier we included preconfigured GitHUB Actions which are helping to maintain properly standardized code during the Code Review process.

Feel free to give it a try – let us know what you think and how it works for you!