https://github.com/webdevstudios/oops-wp-demo
An example plugin to demonstrate usage of OOPS-WP structures and utilities.
https://github.com/webdevstudios/oops-wp-demo
Last synced: 9 months ago
JSON representation
An example plugin to demonstrate usage of OOPS-WP structures and utilities.
- Host: GitHub
- URL: https://github.com/webdevstudios/oops-wp-demo
- Owner: WebDevStudios
- Created: 2020-01-31T17:24:51.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2023-01-05T06:23:08.000Z (over 3 years ago)
- Last Synced: 2025-03-27T13:45:09.605Z (about 1 year ago)
- Language: PHP
- Size: 3.34 MB
- Stars: 5
- Watchers: 4
- Forks: 1
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# OOPS-WP Demo
This is a companion repository to the [OOPS-WP](https://github.com/webdevstudios/oops-wp) project.
It provides code examples for the various structures and utilities provided by the OOPS-WP
library.
## Requirements
This example requires that you have [Composer](https://getcomposer.org)
and [Git](https://git-scm.org) installed on your computer, and that you
are also familiar with how to set up a local WordPress installation.
## Installation
Ideally, your project would require this plugin via Composer:
`composer require webdevstudios/oops-wp-demo`
Depending on where your vendor directory is configured to install, you
would then require the Composer autoloader. One approach we like to take
is to [configure Composer to install the vendor directory inside the mu-plugins
directory](https://getcomposer.org/doc/06-config.md#vendor-dir), and create
an `autoloader.php` mu-plugin, so you wind up with the following directory
structure:
/mu-plugins/
- /vendor/
- autoloader.php
Inside autoloader.php, you would include your require statement:
```