PHPackages                             martinherweg/craft-gonzo - 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. [Utility & Helpers](/categories/utility)
4. /
5. martinherweg/craft-gonzo

Abandoned → [haariga/craft-gonzo](/?search=haariga%2Fcraft-gonzo)Craft-plugin[Utility & Helpers](/categories/utility)

martinherweg/craft-gonzo
========================

Component Library from your templates Folder

2.0.0-alpha-2(2y ago)111731[8 issues](https://github.com/haariga/craft-gonzo/issues)[3 PRs](https://github.com/haariga/craft-gonzo/pulls)MITJavaScript

Since Jan 29Pushed 2y ago3 watchersCompare

[ Source](https://github.com/haariga/craft-gonzo)[ Packagist](https://packagist.org/packages/martinherweg/craft-gonzo)[ RSS](/packages/martinherweg-craft-gonzo/feed)WikiDiscussions develop Synced yesterday

READMEChangelog (4)Dependencies (4)Versions (12)Used By (0)

Gonzo — Pattern Library
=======================

[](#gonzo--pattern-library)

[![Screenshot](resources/img/plugin-logo.png)](resources/img/plugin-logo.png)

```
*** BETA **********

!IMPORTANT NOTE!
This plugin is currently under development and requires a special structure in your templates folder to be used.
Please scroll to the Structure example to learn more.
If you have any recommendations on how to improve it please create a ticket on GitHub.

Thank you very much
David & Martin

*******************

```

Demo
----

[](#demo)

You can this plugin in action here:

Description
-----------

[](#description)

Gonzo is the Pattern Library with less effort. You've just created config files to bring your components in the library. It's quite simple. You need no third party tool to have a pattern library. Just write your code as usual but start not with dummy hard written content in your templates. You also need entries in the backend (just some images) to fill your components. Each component have an config.php file and here is all the magic. It's a huge advantage to use gonzo.

The developer can create components decoupled from templates or whole pages. Focus on the component and build all variants for your specific component. When you are done set the status to **review** or something else and give it back to the designer to get an approval. The whole team can see the component status and it's clear for all what's done and what's on development.

A second huge benefit for the team is that you can see all you components on one place. What's not in the library does not exist. It's really clear someone can check which buttons are currently on the project.

Third benefit is you can discuss about specific components with the client without lose the focus.

It's a living library and if your project grows your library will grow too!

---

**Table of contents**

- [Requirements](#requirements)
- [Installation](#installation)
- [Configuration](#configuration)
- [Screenshots](#screenshots)
- [Folder Structure](#structure)
- [Example](#example)
- [Pages](#pages)
- [Roadmap](#roadmap)

---

Requirements
------------

[](#requirements)

This plugin requires Craft CMS 3.0.0 or later.

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

[](#installation)

### Install via composer

[](#install-via-composer)

```
composer require haariga/craft-gonzo
```

### Install via Admin Control Panel

[](#install-via-admin-control-panel)

Go to the Plugin Store and search for: `Gonzo` and install it.

Configuration
-------------

[](#configuration)

### Plugin Config File

[](#plugin-config-file)

You must create a `craft-gonzo.php` file in your config folder. Here is a basic config file you can start with. In the `_examples` folder is a more complex one to create additional pages and stuff like this.

```