PHPackages                             totten/hyde - 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. totten/hyde

ActiveDrupal-module[Utility & Helpers](/categories/utility)

totten/hyde
===========

861

Since May 24Pushed 7y ago2 watchersCompare

[ Source](https://github.com/totten/hyde)[ Packagist](https://packagist.org/packages/totten/hyde)[ RSS](/packages/totten-hyde/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

Drupal is well and good, but I don't like editing pages in a web UI. Or storing them in MySQL. Or configuring workflows. Is that a problem? Can I still use Drupal?

Mr. Hyde is the evil version of Dr. [Jekyll](https://jekyllrb.com/) -- it's a Drupal module that lets you create Markdown files and store them in a git repo... but it displays them as pages in a Drupal site. This allows you to use Drupal's general layout engine (themes and blocks) while tracking content in `git` (and using stock workflows like Github PR's or Gitlab MR's).

Install the module
==================

[](#install-the-module)

```
$ cd sites/all/modules
$ git clone https://github.com/totten/hyde
$ cd hyde
$ composer install
$ drush en hyde

```

> Note: It should be OK to install via `composer require totten/hyde`, but I haven't done enough with D7+Composer to speak to that.

Initialize the content root
===========================

[](#initialize-the-content-root)

```
$ cd
$ mkdir hyde
$ cd hyde

```

Of course, this folder should probably be a git repo. You could initialize a new repo here (`git init`) or clone an existing repo.

> **Tip**: If you want to store content in another folder, override the value of `hyde_path` by calling `drush vset hyde_path /path/to/doc/root`or editing `settings.php`.

Add a new page
==============

[](#add-a-new-page)

```
$ echo "Hello __world__" > hello-world.md
$ drush cc all
$ curl https://example.org/hello-world
$ git add hello-world.md
$ git commit

```

Markdown metadata
=================

[](#markdown-metadata)

In Jekyll syntax, a Markdown file can begin with a YAML metadata. In this example, we set the `title` of the HTML page with a little extra metadata:

```
---
title: "The future of old school content"
---
# Old is the new new
Because sometimes you like to write content in a simple way.

# Git is the new CMS
Because sometimes you like to write content in a simple way.

```

Supported fields:

- `title`: The main HTML page title

Issues/Limitations/FIXMEs
=========================

[](#issueslimitationsfixmes)

There are several things that one might do if they really cared about this. Right now, I'm trying to write this quickly, so I don't really care.

- Add an admin form for manging `hyde_path`
- Test/implement page-cache support.
- Rework as Drupal entity. If a file is writeable, allow editing the `body` via CLI or GUI. If a file is not writeable, then don't.
- Add more options to the metadata for:
    - Setting permissions
    - Changing layouts
- Want to be sure that *only* CLI users can manipulate Markdown files? Just set the file-permissions appropriately.

Coding style
============

[](#coding-style)

This repo is a safe space for godawful code that I wrote in 15 minutes after drinking some beer.

###  Health Score

22

—

LowBetter than 22% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity11

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity41

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.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/1336047?v=4)[Tim Otten](/maintainers/totten)[@totten](https://github.com/totten)

---

Top Contributors

[![totten](https://avatars.githubusercontent.com/u/1336047?v=4)](https://github.com/totten "totten (8 commits)")

### Embed Badge

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

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

PHPackages © 2026

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