Download the PHP package grottopress/jentil without Composer

Jentil

Jentil is a modern framework for rapid WordPress theme development. It emphasizes a cleaner, more modular way of building WordPress themes, without straying too far from the core WordPress API.

Jentil is designed with the SUV architecture, and makes full use of the express power of core WordPress' event driven architecture.

Jentil features a more organised directory structure. Templates are loaded from the templates/ directory, and partials from the partials/ directory.

It is packed with predefined, pluggable features, including powerful content options which allows users to configure how posts display on archives right from the customizer.

Jentil may be installed either as a parent theme, or as a package in another theme.

Features

• Robust architecture, with a more organised directory structure. The days of dumping templates in your theme's root are over!
• Numerous action and filter hooks to allow easy extension via child themes and plugins.
• Clean, object-oriented codebase.
• Modern web development tools.
• Compliant with PSR-1, PSR-2 and PSR-4.
• Powerful posts display options via the customizer.
• Page builder post type templates
• Six (6) layout options
  • Content
  • Content / Sidebar
  • Sidbar / Content
  • Sidebar / Content / Sidebar
  • Content / Sidebar / Sidebar
  • Sidebar / Sidebar / Content
• HTML5 / CSS3
• SEO-ready
• Responsive (mobile-ready)

Requirements

• PHP >= 7.0
• WordPress >= 5.3
• Composer
• Node JS

These are the core requirements you need to get in place. The rest would be installed by the theme itself during installation.

Installation

Install jentil-theme, which is a starter for building your own theme with Jentil:

1. From the wp-content/themes/ directory, run composer create-project --remove-vcs grottopress/jentil-theme your-theme-slug-here.
2. Switch to your-theme-slug-here/ directory: cd your-theme-slug-here/.
3. Update theme information in style.css. You may also want to change package name, description and author in composer.json and package.json.
4. Copy bs-config-sample.js to bs-config.js: cp bs-config-sample.js bs-config.js. Edit to taste.
5. Replace all occurrences of 'jentil-theme' text domain with your own theme slug. Your theme slug should match your theme folder name, which should just be the slugified version of your theme's name.
6. Do a git init to initialize a new git repository for your theme.
7. Run vendor/bin/wp theme activate your-theme-slug-here to activate your new theme.
8. Dive into your theme's source, and start developing.

Install Jentil as parent theme

By default, your new theme is installed with Jentil as package (in the vendor/ directory). This is recommended.

However, Jentil is a full-fledged WordPress theme by itself, and can, therefore, be installed as such.

If, for any reason, you would like to use Jentil as parent theme instead, follow the steps below:

1. Add Template: jentil to your theme's style.css headers.
2. Run composer remove grottopress/jentil to remove Jentil from your theme's dependencies.
3. Swicth to wp-content/themes/ directory: cd ../
4. Install Jentil as (parent) theme: composer create-project grottopress/jentil jentil
5. Switch to your own theme's directory: cd your-theme-slug-here/
6. Activate your own theme (not Jentil), if not already active.

Install via Docker

Your new theme has docker files in the docker/ directory. The following Dockerfiles are available:

• apache.Dockerfile: Builds an image of WordPress + PHP + apache, with your theme installed.
• apache.child.Dockerfile: Builds an image of WordPress + PHP + apache, with your theme installed as child theme of Jentil.
• fpm-alpine.Dockerfile: Builds an image of WordPress + PHP-FPM, with your theme installed.
• fpm-alpine.child.Dockerfile: Builds an image of WordPress + PHP-FPM, with your theme installed as child theme of Jentil.

You may build an image using any of the Dockerfiles:

You may run your built image thus:

Developing your theme

Whether Jentil is installed as theme or package, it acts as a parent theme, in the WordPress sense. This means your theme inherits all features of Jentil.

You can remove or override Jentil's features, just as you would any WordPress parent theme; via remove_action or remove_filter calls in your own theme.

You may override templates and partials by placing a similarly-named template or partial in the templates/ or partials/ directory of your theme, respectively.

Your own theme's singleton instance is available via a call to \Theme() (unless you changed it in app/helpers.php), while Jentil's is available via \Jentil(). You may use these in files outside app directory (eg: in templates and partials) to access the respective instances.

The Jentil singleton instance is exposed as the $parent attribute in the main Theme class (app/Theme.php).

Directory Structure

The directory structure for your theme, after installation, should be similar to this:

Adding templates and partials

Templates and partials should be filed in templates/ and partials/ respectively. The rules and naming conventions are as defined by WordPress. Therefore, a templates/singular.php in your theme overrides the same in Jentil.

If you decide to add your own templates, do not use WordPress' \get_header(), \get_footer() and \get_sidebar() functions in them. These functions expect your partials to be in your theme's root, and WordPress provides no way of overriding those.

Jentil uses it's own loader to load partials from the partials/ directory. You should call eg: \Jentil()->utilities->loader->loadPartial('header', 'some-slug'), instead of \get_header('some-slug').

Template hooks

You should rarely need to add your own templates, as Jentil comes with template hooks you can use to add or remove stuff from the bundled templates.

The following action hooks are available:

• jentil_before_header
• jentil_inside_header
• jentil_after_header
• jentil_after_after_header
• jentil_before_before_title
• jentil_before_title
• jentil_after_title
• jentil_before_content
• jentil_after_content
• jentil_after_after_content
• jentil_before_before_footer
• jentil_before_footer
• jentil_inside_footer
• jentil_after_footer

Post type templates

WordPress introduced post type templates in version 4.7, as an extension of page templates to all post types. WordPress looks for post type templates in the root of your theme.

Jentil's loader does not load any template (or partial) from your theme's root at all. So if you placed post type templates here, though they may be recognised by WordPress and listed in the Page Template dropdown in the post edit screen, they would not be loaded by Jentil.

To use post type templates in your own theme, add the templates in the templates/ directory, and use the theme_{$post_type}_templates filter.

Jentil uses this hook to add page builder templates, and provides an AbstractPostTypeTemplate setup class your theme's post type templates can inherit from.

Styling

Jentil's styles are designed to be used, so we do not encourage that you dequeue it, unless you intend to recompile and enqueue in your own theme.

Care has been taken to make them as basic as possible, so they do not get in your way. You can simply enqueue your own theme's style sheet(s) after Jentil's.

Testing

Jentil employs, and encourages, proper, isolated unit tests. jentil-theme comes with WP Browser and Function Mocker for testing. You may swap these out for whatever testing framework you are comfortable with.

WP Browser uses Codeception, which, in turn uses PHPUnit, so it should take care of most testing needs. In addition to unit tests, you may add integration, functional and acceptance tests, using the same setup.

Run all tests with composer run test, as defined in composer.json, under scripts configuration.

Architecture

Jentil is desinged using the SUV architecture. You might want to check that out, as it may give a better understanding of the core philosophy underpinning Jentil's development.

Showcase

The following projects are powered by Jentil:

• GrottoPress
• Ghana Gong
• iQ College
• Betta WordPress theme

Development

Run tests with composer run test.

Contributing

1. Fork it
2. Switch to the master branch: git checkout master
3. Create your feature branch: git checkout -b my-new-feature
4. Make your changes, updating changelog and documentation as appropriate.
5. Commit your changes: git commit
6. Push to the branch: git push origin my-new-feature
7. Submit a new Pull Request against the GrottoPress:master branch.