Home
Zeever is an initiative to create a new opinionated theme for Backdrop CMS to serve the interests of Digital Agencies and related businesses and is inspired by a Wordpress Theme by the same name, Zeever.
By opinionated, we mean to suggest that the Zeever theme will be designed with specific layouts and functionality in mind. While we will try to support all of the core layouts, our focus with this theme is the specific configuration and content provided by the "Digital Agency" recipe package and the following recipes which are required by Digital Agency.
We are inviting others to provide feedback, ideas, and PR contributions very early in the development of this project. For now, let's keep all issues for THEME and MODULE in this issue queue: https://github.com/backdrop-contrb/zeever/issues
- To experiment with mixing a theme, a complementary module, and config recipes to allow someone to quickly spin-up an attractive and functional website with sample content, suitable for a specific use case (in this case, a Digital Agency). Something like an install profile, but something you can add to an existing site.
- To push the boundaries of "recipes" for Backdrop CMS.
- To encourage experimentation and ideas to make it eaiser to build "no-code" websites with Backdrop CMS.
- To make this project work well with the features and methods of Backdrop CMS core and through development of this theme and it's associated module inspire improvements in Backdrop core. We should not let limitations in core block development of this theme and it's associated module.
- To make it possible to spin-up a working Zeever styled site by installing and enabling nothing more than the Zeever theme along with the Digital Agency recipe package and dependencies. These two actions should be enough to have a fully working site.
- To use the Zeever theme for Wordpress as our guide, but to allow ourselves to make small or large changes to meet the needs of this project. We should stay close to the Zeever theme only in so far as it helps move us along without the need to make large design decisions, but still feel free to make changes as needed.
- We MAY work under the assumption that the Zeever Config module is being installed in a relatively fresh site. We do not need to constrain ourselves by trying to avoid namespace problems. This module is intended to be used early in the development process for a site when there is a little existing configuration that one might collide with.
- We do NOT expect there to be an "uninstall" path for this module or the recipes that come with it. We will provide instructions on how to test the module before installing it on a site where it might be difficult to remove.
We encourage feedback and participation in this project. We would like to learn from others and stimulate community discussion on best practices and expectations for this kind of project.
This theme is intended to be an idea fork of a Wordpress theme with the same name. https://gutenverse.com/demo?name=zeever
We refer to this as an idea fork, rather than a port or code fork, because at this point in the development of this theme, we have not yet decided to take any code directly. Rather, we may simply rebuild the theme based upon it's design and functionality.
The intention is that this theme will be built with specific functionality in mind and sample content to get started. This theme will come with a recommendation to use it in conjunction with the "Digital Agency" package/module. The Digital Agency package/module will be dependent upon specific recipes that will generate content types, fields, views, and other configuration that work well with the theme.
As much as possible, we will leave any code or specific sample content to the Digital Agency package/module, keeping the related recipes as clean as possible (clean = config files only). The recipes will all provide useful features on their own, with or without Zeever theme or Digital Agency package/module. As much as possible, we will reuse existing config recipes and create new ones as needed to complete this project.
At completion, it should be possible to use either the Zeever theme or the Digital Agency package/module on their own. But, we expect that they will both be most useful when used in combination. More than one theme might support the Digital Agency package/module.
