WP Manifestindependent plugin directory
manifest / content / wp-pvtl-recipes

PVTL Recipes

Adds a recipe custom post type, taxonomy and fields

by Pivotal Agency · github.com/pvtl/wp-pvtl-recipes · website

0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/pvtl/wp-pvtl-recipes/archive/refs/heads/main.zip

Readme

Recipe Wordpress Plugin by Pivotal Agency

  • A recipe custom post type
  • A recipe-category taxonomy
  • Recipe fields added to the post type
  • Front-end templates (listing and single) to output the fields

Prerequisites

  • Wordpress
  • Advanced Custom Fields Pro installed and activated

The default front-end templates make use of Foundation - however you can override these in your theme if you need something different.

Installation

*The following should be run from your plugins directory

git clone https://github.com/pvtl/wp-pvtl-recipes.git
  • Activate the plugin
  • Update the project's .gitignore so that the plugin is included in the repo

How do I...?

Modify the front-end layout?

By default, the plugin will use the templates found in <plugin_dir>/resouces/views/*.php.

You can easily override these templates, by creating the respective templates in your theme, naming them:

File Name Desc.
single-recipe.php The single post template (overrides single.php)
archive-recipe.php The listing template (overrides archive.php)

Add extra fields?

Are the extra field/s specific for this project?

  • Simply create a new ACF group and add the fields, targeted to this post type
  • You'll then need to override the front-end template/s to output the additional fields

Should these new field/s be default for all projects?

  • Import the /custom-fields/acf-export.json into ACF > Tools
  • Modify the fields
  • Export the JSON file + Generate the PHP (replacing the existing files)
  • Update the front-end templates to include the fields
  • Commit the changes back to the GIT repo

Read the full README on GitHub →