PHPackages                             em4nl/unplug - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. em4nl/unplug

ActiveLibrary[Framework](/categories/framework)

em4nl/unplug
============

WordPress microframework

v0.0.15(6y ago)5116[2 issues](https://github.com/em4nl/unplug/issues)MITPHPPHP >=5.6CI failing

Since Feb 22Pushed 6y ago2 watchersCompare

[ Source](https://github.com/em4nl/unplug)[ Packagist](https://packagist.org/packages/em4nl/unplug)[ Docs](https://github.com/em4nl/unplug)[ RSS](/packages/em4nl-unplug/feed)WikiDiscussions master Synced 3w ago

READMEChangelogDependencies (4)Versions (18)Used By (0)

Unplug
======

[](#unplug)

WordPress microframework

Installation
------------

[](#installation)

Via composer:

```
composer require em4nl/unplug
```

Usage
-----

[](#usage)

Unplug is a microframework for use in a WordPress theme when you need more control over the frontend of your website than WordPress gives you by default. It's highly recommended to use it together with the [Twig](https://twig.symfony.com/Homepage) template engine.

The basic idea is to bypass WordPress' routing/template hierarchy mechanisms completely and roll our own.

I assume you're using autoloading and your composer vendor dir is at `./vendor`.

### functions.php

[](#functionsphp)

To make sure WordPress doesn't run its default query/template, you'll need to add a call to `Em4nl\Unplug\unplug` in your theme's `functions.php`.

```