Composer

Composer is a package manager for PHP packages, and can be used to install WP plugins as well as libraries needed for JCORE®. Composer is used in different degrees in different projects. Sometimes it is only used to install Timber and ACF, and sometimes to manage all plugins in the project.

Plugins & Packages required in JCORe (the starter set)

Plugins that are always part of the JCOre base setup and what they do. The list will in most cases be extended on a project basis.

"timber/timber":

Drives the whole twig-theme template structure

"jco/advanced-custom-fields-pro":

Adds the custom fields (to block and theme)

"jco/wp-migrate-db-pro":

WP db migration plugin. Can be used in publication for database changes.

"wpackagist-plugin/better-search-replace":  

A lighter option for database changes than wp-migrate-db-pro.

"sentry/sentry": 

Sentry is a crash reporting platform that provides you with real-time insight into production deployments with info to reproduce and fix crashes.

"symfony/http-client": 

Standalone PHP library providing a specific feature, which can be used in any PHP application.

"wpackagist-plugin/wordpress-seo": 

YOAST -for seo and social media

"nyholm/psr7": 

A fast PHP7 implementation of PSR-7. Required by symfony.

"wpackagist-plugin/wp-bootstrap-blocks":  

Adds functioning columns with media queries. (Do not use the columns-block native to G-berg. Responsivity is lacking, or add media queries yourself. )

"wpackagist-plugin/redirection":  

To redirect urls from the WP backend.

"jco/minimal-coming-soon-maintenance-mode":  

Plugin for coming soon pages.

"jco/webtoffee-gdpr-cookie-consent":  

Webtoffee gdpr popup

"jco/gravityforms": 

For form handling.

"jco/polylang-pro":  

For multilingual sites.

"wpackagist-plugin/mailgun":  

An email automation engine for configuration and routing.

Development Plugins & Packages

These plugins are only in use in development environment via require-dev in composer.

"wpackagist-plugin/pattern-manager":

Easily create and manage block patterns in the backend that are automatically saved as php.

"wpackagist-plugin/loco-translate":

Create string translations locally for pushing to git.

"squizlabs/php_codesniffer": "^3.7",
"dealerdirect/phpcodesniffer-composer-installer": "^1.0",
"wp-coding-standards/wpcs": "dev-develop",

These three packages are used for setting up WordPress Coding Standards for PHP_CodeSniffer in the project.

Languages and tranlations

JCOre adds loco translate locally, and the theme/languages -folder contians a jcore.pot -file. The projects "small words" are translated for ex on a Swedish site in development, and the plugin should not be added to composer. Translations are pushed with the project.

"wpackagist-plugin/loco-translate":

-Only move to require from require-dev in composer if the CUSTOMER him/herself needs access and does translations themselves. -Then locotranslate needs to be added to composer, activated and a CUSTOM translation added on live, for it not to be overwritten by push.