PHPackages                             grimmdude/jebson - 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. grimmdude/jebson

ActiveLibrary

grimmdude/jebson
================

A content management system based on static files aimed at ease of use and swift load times.

18PHP

Since Feb 16Pushed 3y ago1 watchersCompare

[ Source](https://github.com/grimmdude/jebson)[ Packagist](https://packagist.org/packages/grimmdude/jebson)[ RSS](/packages/grimmdude-jebson/feed)WikiDiscussions master Synced today

READMEChangelog (1)DependenciesVersions (1)Used By (0)

Jebson CMS
==========

[](#jebson-cms)

 Up until now I've always used Wordpress to manage my website; mainly because it's easy to use and it's what I learned on. It's great in that regard but lately I've been realizing how slow it is. I realized that I didn't even need the media library, special SEO plugins, dynamic nav menus, and widgets. Then I realized, I don't even need a database. I wanted a system that was fast to load, and simple to add content or modify template files. Basically I wanted a static site, but I wasn't too keen on learning a bunch of new terminal commands and re-building every time I write a new post.

 Blah blah blah, so I wrote my own CMS. While it still technically builds each page dynamically it's quick loading, and there's no database to fuss with. I call it `Jebson`, named after one of my pups. Jebson is a very lightweight databaseless CMS that is geared towards simplicity and swift load times. Note that currently I'm writing this is so I will have some documentation for myself so it may not be complete. You'll notice I borrow some stuff from popular static site generators, that's just how I roll.

Setup
-----

[](#setup)

 `Jebson` is written in PHP and is setup to use Apache. To install place all of Jebson's files into your webroot. Now say "yea I did it!".

### Directory Structure

[](#directory-structure)

```
.
   .htaccess
   assets/
   cache/
   content/
      2013-08-22-sample-post.php
      sample-page.php
   config.php
   index.php
   lib/
   views/
      404.php
      body.php
      excerpt.php
      footer.php
      header.php
      post.php
```

All of the settings for Jebson can be found in the Config class ([config.php](https://github.com/grimmdude/jebson/blob/master/config.php)).

Views
-----

[](#views)

 These are the common files that get loaded on each page like the header, footer, etc... All views are `.php` files and live in the `/views` directory. Below are the variables that you'll need to echo in your view to output content and other available data.

### View Variables

[](#view-variables)

   Variable Description     `self::$request` Contains an array of the segments in the request URL.   `self::$content` The juice. This holds the content.   `self::$excerpt` Holds a post excerpt.   `self::$loadTime` Holds the number of seconds it took to load the page.   `self::$pageData` Array of data defined at the top of each piece of content.   `self::$date` Contains the date for blog posts in this format: MM-DD-YYYY. If not available, this variable will be set to `false`.  To define the load order for the views use the config array `Config::$viewLoadOrder`

### View Methods

[](#view-methods)

   Method Description     `self::renderContent()` Typically will be placed in the body of your site. This method checks the requested URL and sets up the appropriate content.  Writing Content
---------------

[](#writing-content)

 All content is saved as `.php` files in the `/content` directory and markup is standard HTML. Naming conventions are as follows:

### Posts

[](#posts)

For posts which are to be sorted by date:

```
2013-08-22-url-of-the-post.php
```

This will result in a post url like so:

```
website.com/2013/08/22/url-of-the-post
```

### Pages

[](#pages)

For pages, that is content not considered a dated post, just leave out the date:

```
title-of-my-page.php
```

Which results in this url:

```
website.com/title-of-my-page
```

Each file starts off with some basic properties to define stuff:

```

```

 These variables are available in the views and can be used how you wish. Obviously I'd use these basic definitions for page meta data, but you can also add your own custom definitions to trigger things like comments, layouts, scripts, css, etc.

###  Health Score

15

—

LowBetter than 3% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity23

Early-stage or recently created project

 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/376199?v=4)[Garrett Grimm](/maintainers/grimmdude)[@grimmdude](https://github.com/grimmdude)

---

Top Contributors

[![grimmdude](https://avatars.githubusercontent.com/u/376199?v=4)](https://github.com/grimmdude "grimmdude (60 commits)")

### Embed Badge

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

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

PHPackages © 2026

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