PHPackages                             tagmeo/tagmeo - 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. tagmeo/tagmeo

ActiveProject

tagmeo/tagmeo
=============

A modern WordPress stack with the latest development tools, easier configuration, enhanced security, and an improved folder structure.

v0.0.1(9y ago)014MITPHPPHP &gt;=5.6

Since Jul 20Pushed 9y ago1 watchersCompare

[ Source](https://github.com/tagmeo/tagmeo)[ Packagist](https://packagist.org/packages/tagmeo/tagmeo)[ Docs](https://tagmeo.com)[ RSS](/packages/tagmeo-tagmeo/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (1)Dependencies (5)Versions (3)Used By (0)

Tagmeo
======

[](#tagmeo)

[![Build Status](https://camo.githubusercontent.com/3c3e9bc7bfecc386df2531079b70eda798284eb37c93c4aa453af2fdaeebe799/68747470733a2f2f7472617669732d63692e6f72672f7461676d656f2f7461676d656f2e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/tagmeo/tagmeo) [![Latest Stable Version](https://camo.githubusercontent.com/59ea046e6e614360a9f5be7837e7673cbf3bdb639541a2e377bbfee3991cc52c/68747470733a2f2f706f7365722e707567782e6f72672f7461676d656f2f7461676d656f2f762f737461626c65)](https://packagist.org/packages/tagmeo/tagmeo) [![Latest Unstable Version](https://camo.githubusercontent.com/c64c3ee34ee6762153fbce9ca4c90c560ad19582bfe652e6bff8e368901cf84b/68747470733a2f2f706f7365722e707567782e6f72672f7461676d656f2f7461676d656f2f762f756e737461626c65)](https://packagist.org/packages/tagmeo/tagmeo) [![License](https://camo.githubusercontent.com/8b04d0356f46074ca3c7db8039bf900d84ba5a5baec027683393423dd8ecf9b4/68747470733a2f2f706f7365722e707567782e6f72672f7461676d656f2f7461676d656f2f6c6963656e7365)](https://packagist.org/packages/tagmeo/tagmeo) [![composer.lock](https://camo.githubusercontent.com/bc94f4c0c6a10dd3fcfa9110f4a6a15f7c047dd08317d34ab719cfcbf986d506/68747470733a2f2f706f7365722e707567782e6f72672f7461676d656f2f7461676d656f2f636f6d706f7365726c6f636b)](https://packagist.org/packages/tagmeo/tagmeo)

A modern WordPress stack with the latest development tools, easier configuration, enhanced security, and an improved folder structure.

- [Installation](#-installation)
    - [Server Requirements](#server-requirements)
    - [Installing Tagmeo](#installing-tagmeo)
        - [Via Tagmeo Installer](#via-tagmeo-installer)
        - [Via Composer Create-Project](#via-composer-create-project)
        - [Via Git Clone](#via-git-clone)
- [Folder Structure](#-folder-structure)
- [Environment](#-environment)
- [Assets](#-assets)
    - [Gulp](#gulp)
    - [NPM](#npm)
- [WordPress](#-wordpress)
    - [Plugins](#plugins)
    - [MU Plugins](#must-use-mu-plugins)
    - [Themes](#themes)
- [Resources](#-resources)
    - [SCSS](#scss)
    - [Asset Loader](#asset-loader)
        - [Parameters](#parameters)
        - [Examples](#examples)
- [Console Application](#-tagmeo-console)
- [Vagrant](#-vagrant)
- [Laravel Valet](#-laravel-valet)

[\#](#-installation) Installation
---------------------------------

[](#-installation)

### [](#server-requirements)Server Requirements

[](#server-requirements)

Tagmeo has a few system requirements. Of course, all of these requirements are satisfied by the [Vagrant](#-vagrant) virtual machine that's included, so it's highly recommended that you use this for your local development environment.

If you're not using Vagrant, you will need to make sure your server meets the following requirements:

- MySQL &gt;= 5.5.9
- Node &gt;= 5.9
- NPM &gt;= 3.7
- PHP &gt;= 5.6

You'll also need the following PHP extensions:

- Mbstring
- OpenSSL
- PDO
- Tokenizer

### [](#installing-tagmeo)Installing Tagmeo

[](#installing-tagmeo)

Tagmeo uses [Composer](http://getcomposer.org) to manage its dependencies. So, before using Tagmeo, make sure you have Composer installed on your machine.

#### [](#via-tagmeo-installer)Via Tagmeo Installer

[](#via-tagmeo-installer)

First, download the Tagmeo installer using Composer:

```
composer global require tagmeo/installer
```

Make sure to place the `~/.composer/vendor/bin` directory (or the equivalent for your OS) in your `PATH` so the `tagmeo` executable can be located by your system.

Once installed, the `tagmeo new` command will create a fresh Tagmeo installation in the directory you specify. For example, `tagmeo new blog` will create a directory named `blog` containing a fresh installation with all of the dependencies already installed. This method of installation is much faster than installing via Composer:

```
tagmeo new blog
cd blog
php tagmeo setup
```

The last command will walk you through the setup process to create your environment file, generate WordPress authentication keys and salts, install NPM packages, run Gulp, and provision your virtual machine.

#### [](#via-composer)Via Composer

[](#via-composer)

You can install Tagmeo by issuing the Composer `create-project` command:

```
composer create-project tagmeo/tagmeo blog
cd blog
php tagmeo setup
```

#### [](#via-git)Via Git

[](#via-git)

If you prefer, you can install Tagmeo by cloning the repository:

```
git clone https://github.com/tagmeo/tagmeo blog
cd blog
composer install
php tagmeo setup
```

[\#](#-folder-structure) Folder Structure
-----------------------------------------

[](#-folder-structure)

The following `tree` output shows the most commonly used folders and files:

```
├── elixir.json                         # Asset loader
├── gulpfile.js                         # Task automator
├── app                                 # Application framework
├── config
│   └──  application.php                # Primary configuration
├── public                              # Virtual host document root
│   ├── assets                          # Public assets
│   │   └── rev-manifest.json           # Cache busting
│   ├── cms                             # WordPress core
│   ├── mu-plugins                      # WordPress must-use plugins
│   ├── plugins                         # WordPress plugins
│   ├── themes                          # WordPress themes
│   └── uploads                         # WordPress uploads
├── resources
│   └── assets                          # Local assets
├── vendor                              # Composer dependencies
└── tagmeo                              # Console application

```

[\#](#-environment) Environment
-------------------------------

[](#-environment)

The `.env` file controls your environment settings. For security reasons, this file is not stored in the repository, but you can look at the `.env.example` file as a reference. The following variables can be set:

```
AUTH_KEY
AUTH_SALT
DB_CHARSET
DB_COLLATE
DB_HOST
DB_NAME
DB_PASS
DB_PREFIX
DB_USER
DISABLE_CRON
DISABLE_FILE_EDIT
DISABLE_UPDATER
LOGGED_IN_KEY
LOGGED_IN_SALT
NONCE_KEY
NONCE_SALT
SECURE_AUTH_KEY
SECURE_AUTH_SALT
WP_ENV
WP_HOME
WP_SITEURL

```

The following variables are required:

- `DB_NAME`
- `DB_USER`
- `DB_PASS`
- `WP_HOME`
- `WP_SITEURL`

Valid input for the `WP_ENV` variable are:

- `development`
- `staging`
- `production`

[\#](#-assets) Assets
---------------------

[](#-assets)

The `elixir.json` file controls what local or remote scripts or stylesheets are loaded, along with the local and distribution asset folders.

### [](#gulp)Gulp

[](#gulp)

The `gulpfile.js` file handles all of the assets for the project and places them in the `public/assets` folder, along with things like copying files, minification, cache busting, and BrowserSync.

### [](#npm)NPM

[](#npm)

The `package.json` file is where dependencies for `npm` are saved.

[\#](#-wordpress) WordPress
---------------------------

[](#-wordpress)

WordPress is installed in the `public/cms` directory.

### [](#plugins)Plugins

[](#plugins)

Installed plugins reside in `public/plugins`.

### [](#mu-plugins)Must-Use (MU) Plugins

[](#must-use-mu-plugins)

All must-use plugins are in `public/mu-plugins`.

### [](#themes)Themes

[](#themes)

The themes are located in the `public/themes` directory. The default theme is called `tagmeo`, but can be renamed based on the project.

[\#](#-resources) Resources
---------------------------

[](#-resources)

The `resources` directory holds all of the local assets (images, fonts, scripts, stylesheets, etc.) that `gulp` uses to make the `app.css` and `app.js` file in the public distribution folder.

### [](#scss)SCSS

[](#scss)

A default SCSS structure has been setup to speed up the styling process. The `app.scss` file should not contain any CSS, instead, it's where we import partials and vendor files.

The `modules` directory really won't be touched either, besides setting up variables for the theme. No code should reside in these files either.

Finally, the `partials` directory is where the meat of the styling goes, and it's divided up based on the element and/or layout we're dealing with.

### [](#asset-loader)Asset Loader

[](#asset-loader)

All of the CSS and JavaScript assets are setup in the `elixir.json` file. Here's an example of the configuration options available to you:

```
"assets": {
  "[handle]": {
    "file": "[file]",
    "dependsOn": "[dependsOn]",
    "version": "[version]",
    "inFooter": "[inFooter]",
    "media": "[media]"
  }
}
```

#### [](#parameters)Parameters

[](#parameters)

ParemeterTypeRequiredDescription`[handle]`*(string)*YesName of the script or stylesheet.`[file]`*(string)*YesPath to the script or stylesheet relative to the `public/assets` directory. The asset loader knows what type of file you're loading, so you don't have to put that in the path. If you want to specify a path outside of the `public/assets` directory, then use the a relative path from the `asset` or web root to the file. To load an external script or stylesheet, enter the full URL.`[dependsOn]`*(array)*NoAn array of registered handles that the script or stylesheet depends on.`[version]`*(string|boolean)*NoString specifying the script or stylesheet version number, if it has one. Default is `false`.`[inFooter]`*(boolean)*NoWhether to enqueue the script before `` or before ``. Default is `true`.`[media]`*(string)*NoString specifying the media for which the stylesheet has been defined, e.g. (`all`, `screen`, `handheld`, `print`). Default is `all`.#### [](#examples)Examples

[](#examples)

```
"assets": {
  "tagmeo-css": {
    "file": "app.css"
  },
  "akismet": {
    "file": "./plugins/akismet/js/akismet.min.js"
  },
  "authorizer": {
    "file": "../plugins/authorizer/js/authorizer.min.js"
  },
  "bootstrap": {
    "file": "bootstrap.css",
    "version": "3.3.6",
    "media": "screen"
  },
  "jquery": {
    "file": "jquery.js",
    "version": "2.2.3",
    "inFooter": true
  },
  "tagmeo-js": {
    "file": "app.js"
  },
  "tagmeo-customizer": {
    "file": "customizer.js",
    "dependsOn": [
      "jquery",
      "customize-preview"
    ]
  },
  "html5shiv": {
    "file": "//cdn.example.com/js/html5shiv.min.js",
    "version": "3.7.3",
    "dependsOn": [
      "jquery"
    ]
  }
}
```

[\#](#-vagrant) Vagrant
-----------------------

[](#-vagrant)

If you choose to use [Vagrant](https://www.vagrantup.com), please make sure it and [VirtualBox](https://www.virtualbox.org) are installed on your machine.

The default root directory for your project is:

```
/vagrant
```

The following plugins, while not required, are recommended:

- `vagrant-hostmanager`
- `vagrant-auto_network`
- `vagrant-cachier`

You can run the following command to see what plugins you have installed:

```
vagrant plugin list
```

And the following command to install a plugin:

```
vagrant plugin install
```

[\#](#-laravel-valet) Laravel Valet
-----------------------------------

[](#-laravel-valet)

Alternatively, you can use [Valet](https://laravel.com/docs/master/valet) to test your site locally. Once you've finished [installing Valet](https://laravel.com/docs/master/valet#installation), you can load the custom driver:

```
cd ~/.valet/Drivers/
git clone https://github.com/tagmeo/valet .
valet restart
```

###  Health Score

23

—

LowBetter than 27% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity49

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Unknown

Total

1

Last Release

3583d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/2dac3bfbf0725af54c6dd5763bcf5b7c586fd71fbb470e7b6218e8ae0092546c?d=identicon)[divspace](/maintainers/divspace)

---

Top Contributors

[![tagmeo](https://avatars.githubusercontent.com/u/18195586?v=4)](https://github.com/tagmeo "tagmeo (1 commits)")

---

Tags

composerlaravelwordpressjquerysassbootstrapgulpvagrantelixirtagmeomoteo

###  Code Quality

TestsPHPUnit

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/tagmeo-tagmeo/health.svg)

```
[![Health](https://phpackages.com/badges/tagmeo-tagmeo/health.svg)](https://phpackages.com/packages/tagmeo-tagmeo)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
