Download the PHP package maartenvangelder/wordpress without Composer

On this page you can find all versions of the php package maartenvangelder/wordpress. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package wordpress

Wordpress Scaffold

A WordPress 'Pro' scaffold, based on the Bedrock WordPress boilerplate, with a customized theme loosely based on Sage.

Based on

Quick start

Create a new project

Run composer create-project grrr-amsterdam/wordpress-scaffold <project>. This will create a new project in the chosen directory. It will also initiate an interactive shell where the following things will be done for you:

Theme & asset building

We use Yarn for managing our front-end dependencies, and (grrr-gulpfile)[https://github.com/grrr-amsterdam/gulpfile] for building all the assets. Commands should be run from inside the theme folder: web/app/themes/*.

Deploying

We use Capistrano for deployments. Run bundle install to install the necessary requirements, or run gem install bundler first if you don't have Bundler.

Initial server setup can be done via cap <env> deploy:setup, after verifiying that the server config is correct in config/deploy/<env>.rb This will create a few directories, install Composer and WP-CLI, and copy some files which need to be persistent between deploys (eg. files in de shared folder).

Deployments and rollbacks can be done via:

cap <env> deploy and cap <env> deploy:rollback

Structure & flow

Theme settings & logic

We try to avoid extensive logic in templates or partials. Most logic can be found in lib\<namespace>, and all classes are autoloaded thru PSR-4. Directories with classless functions (like libs/Grrr/Utils and libs/Sage/) need to be specified explicitly in the functions.php. Loading them thru Composer will fail, since we 'hoist' the theme composer dependencies to the main composer.json on install.

Plugins & dependencies

WordPress and WordPress plugins should be required by Composer in the root of the project. Dependencies explicitly required by the theme (a SDK for accessing an API for example) should be included in the theme, which has its own composer.json.

Requiring a plugin works by using WordPress Packagist:

Paid plugins should be included in the repo, and excluded form exclusion in the .gitignore file.

Updating WordPress & plugins

Updating WordPress or plugins is as simple as running composer update johnpbloch/wordpress or composer update for everything. Paid plugins can be updated in development, whereafter the updated files can be committed to the repo.

All versions of wordpress with dependencies

PHP Build Version
Package Version
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package maartenvangelder/wordpress contains the following files

Loading the files please wait ...