Download the PHP package pragmaticweb/customisable-archive-templates without Composer
On this page you can find all versions of the php package pragmaticweb/customisable-archive-templates. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pragmaticweb/customisable-archive-templates
More information about pragmaticweb/customisable-archive-templates
Files in pragmaticweb/customisable-archive-templates
Package customisable-archive-templates
Short Description > Customise the WordPress term archive template with the block editor.
License GPL-3.0-only
Homepage https://pragmatic.agency/
Informations about the package customisable-archive-templates
Customisable Archive Templates
A project by Pragmatic.
Customise the WordPress term archive template with the block editor.
- Requirements
- Installation
- Development Process
Requirements
Usage Requirements
Ensure you have the prerequisite software installed:
Installation
Install this plugin with Composer: composer require pragmaticweb/customisable-archive-templates
. Activate the plugin in your WordPress in the usual manner.
Edit a taxonomy term, and enable "Use Template". Set "Template Post ID" to a Post ID of any kind of WordPress post object. This post will be rendered onto the taxonomy archive URL for the specific term.
After that, create a custom taxonomy-{taxonomy_name}.php
template in your theme and customise it for your requirements. We suggest duplicating a single post template like page.php
.
The first post in the template loop will be the "Template Post" you selected earlier; everything subsequent will be the standard list of all posts that are assigned to the current taxonomy term.
You can choose to split the loop and render both parts in different places (e.g. a "see more xyz content" footer), or just render the main "Template Post" and skip the rest of the template loop with a break
instruction inside the loop.
Development Process
This plugin mostly follows the standard Git Flow model.
Workflow
Development happens in feature branches, which are merged into develop
, and then eventually merged into trunk
for deployment to production. When making changes, a feature branch should be created that branches from develop
(and the corresponding pull request should use develop
as the target branch).
Scripts and Tooling
composer run lint:phpcs
-- checks PHP files for compatibility with the WordPress-VIP-Go standards.composer run lint:phpcompat
-- checks PHP files for compatibility with PHP 7.3.