Case Studies by Pivotal
A Wordpress Plugin adding a Case Studies post type
by Pivotal Agency · github.com/pvtl/wp-case-studies · website
★ 2stars
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-case-studies/archive/refs/heads/master.zipReadme
Case Study Wordpress Plugin by Pivotal
- A
case-studycustom post type - A
case-study-categorytaxonomy - Case Study 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
If you're using Bedrock:
git clone https://github.com/pvtl/wp-case-studies.git web/app/plugins/pvtl-case-studies
rm -rf web/app/plugins/pvtl-case-studies/.git- Activate the plugin
- Update the project's
.gitignoreso that the plugin is included in the repo
Alternatively:
- Download this repo as a zip
- Upload the archive to your Wordpress plugin directory and activate the plugin
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-case-study.php |
The single post template (overrides single.php) |
archive-case-study.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.jsoninto 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