PHPackages                             automad/theme-skeleton - 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. automad/theme-skeleton

ActiveAutomad-package

automad/theme-skeleton
======================

An Automad theme package skeleton including tutorial templates for developers

1.1.0(5y ago)21.7k1MITHack

Since Dec 15Pushed 3mo ago1 watchersCompare

[ Source](https://github.com/marcantondahmen/automad-theme-skeleton)[ Packagist](https://packagist.org/packages/automad/theme-skeleton)[ GitHub Sponsors](https://github.com/marcantondahmen)[ RSS](/packages/automad-theme-skeleton/feed)WikiDiscussions master Synced today

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

Automad Theme Skeleton
======================

[](#automad-theme-skeleton)

Important

Please use the new and modern [theme starter kit](https://github.com/automadcms/automad-theme-starter-kit) instead of this repository in order to get started with a new theme.

You can use this package as a package skeleton for new [Automad](https://automad.org) themes. It includes all files to get you started with your own themes quickly. However there is only one single template file with a simple tree menu. While its functionality is reduced to a minimum, it covers most aspects of theme developing regarding the Automad [template language](https://automad.org/developer-guide/building-themes). The beautiful [Bulma](https://bulma.io) CSS framework is used to style the template and therefore this package doesn't include any CSS or JS files.

---

- [Included Templates](#included-templates)
- [Development Workflow](#development-workflow)
    - [The Local Package](#the-local-package)
    - [Create a Git Repository](#create-a-git-repository)
    - [Register Your Package](#register-your-package)
- [Cheat Sheets](#cheat-sheets)

Included Templates
------------------

[](#included-templates)

This package contains these simplified templates that only serve demonstrational purposes:

1. The `page.php` template represents a basic page with a navbar, a content area and a sidebar with menu.
2. The `pagelist.php` template contains a filterable and sortable pagelist that can be used as a skeleton for blogs or portfolios.
3. The `session.php`template demonstrates the usage of session variables and the `set` function.
4. The `images.php` template provides a minimal example of how to build a gallery template.

> ☝️ To see those templates in action while playing around just apply them to any page in your installation!

Development Workflow
--------------------

[](#development-workflow)

This very detailed in-depth guide describes step by step the workflow of setting up and publish a new theme using [Composer](https://getcomposer.org). You can probaly skip some of the points in case you have been working already with Composer in the past.

> ☝️ This guide assumes you're familiar with Visual Code Studio and working on a system with a Bash shell or similar — like macOS or Linux. However, it is of course possible to do the same on a Windows PC — just slightly different.

### The Local Package

[](#the-local-package)

1. It's a good practice to start developing a new package outside of the Automad packages directory. Therefore change to some directory outside of Automad where you want to develop your new theme. Let's assume you want to put your package into a directory called `dev` within your home folder.

    ```
    cd ~/dev

    ```
2. Create new skeleton theme in your `dev` directory using Composer.

    ```
    composer create-project automad/theme-skeleton my-theme

    ```
3. Change to the new theme directory and edit the `composer.json` and `theme.json` files. VS Code is used here as the editor. At least change the vendor and theme name.

    ```
    cd my-theme
    code composer.json

    ```

    Also edit the name in `theme.json`.

    ```
    code theme.json

    ```
4. Now change to your Automad root directory. For example `~/Sites/automad-site`.

    ```
    cd ~/Sites/automad-site

    ```
5. Edit the `composer.json` file of the Automad installation.

    ```
    code composer.json

    ```

    Add the following snippet to Automad's composer file (note the path to your package).

    ```
    {
        ...
        "repositories": [
            {
                "type": "path",
                "url": "~/dev/my-theme"
            }
        ],
        ...
    }

    ```
6. Still in the Automad directory run the following Composer command.

    ```
    composer require my-vendor/my-theme:@dev

    ```

    Now your theme is available in Automad and you can start developing your templates. After all the setup it's now time to create a repository for your theme.

### Create a Git Repository

[](#create-a-git-repository)

When developing is done, it's time to publish your work.

1. Init new Git repository and commit files.

    ```
    cd ~/dev/my-theme
    git init
    git add .
    git commit -m "First commit"

    ```
2. Create a first release tag for your finished theme following the semantic versioning scheme.

    ```
    git tag -a 1.0.0 -m "my version 1.0.0"

    ```
3. Create a new repository on [GitHub](https://github.com).
4. Now, add its URL as a remote to your local repository and push changes. When creating a repository, the URL will be printed on the GitHub page.

    ```
    git remote add origin /remote/URL/of/your/new/repo
    git push -u origin master

    ```

### Register Your Package

[](#register-your-package)

Now it's time to submit your theme package to [Packagist](https://packagist.org). After succseffuly registering it, it will automatically show up in the package [browser](https://packages.automad.org).

Cheat Sheets
------------

[](#cheat-sheets)

In case you prefer to start developing a theme or extension without reading the full documention, the [Cheat Sheets](https://automad.org/developer-guide/cheat-sheets) are a good point to start.

###  Health Score

40

—

FairBetter than 87% of packages

Maintenance55

Moderate activity, may be stable

Popularity21

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity63

Established project with proven stability

 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

Every ~434 days

Total

3

Last Release

1832d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/7a3565413eb5da0526ac25a008fa743c1cd4f30ef1fd5eb17bcfee7e8c6ac5be?d=identicon)[marcantondahmen](/maintainers/marcantondahmen)

---

Top Contributors

[![marcantondahmen](https://avatars.githubusercontent.com/u/8440030?v=4)](https://github.com/marcantondahmen "marcantondahmen (46 commits)")

---

Tags

automadcomposerthemetheme

### Embed Badge

![Health badge](/badges/automad-theme-skeleton/health.svg)

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

###  Alternatives

[dahmen/automad-terminal

A minimal Automad blog theme for terminal lovers

532.2k](/packages/dahmen-automad-terminal)

PHPackages © 2026

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