|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Feather||513||2 years ago||5||mit||Swift|
|Feather is a modern Swift-based content management system powered by Vapor 4.|
|Eloquent Driver||82||14 days ago||2||January 11, 2021||12||mit||PHP|
|A package that allows you to store Statamic entries in a database.|
|Cockpit Sql Driver||29||a year ago||6||April 27, 2021||mit||PHP|
|SQL Driver for Cockpit CMS|
|Cloud CMS application server module for Node.js / Express. This module provides middleware for virtualized content retrieval, cluster-wide caching and broadcasting, tag processing and much more. It is available to be used in building Node.js-based applications that run against Cloud CMS.|
|Kirby Mandrill Driver||9||8 years ago||mit||PHP|
|The missing mail driver for the awesome Kirby CMS.|
|10layer Ls||7||9 years ago||1||other||PHP|
|Fal Flysystem||5||7 years ago||gpl-3.0||PHP|
|[WIP] File Abstraction Layer driver for TYPO3 CMS that uses Flysystem|
This code supports the demo from the Everything is a CMS! talk from Next.js Conf 2020.
Its purpose is to demonstrate that we can easily swap data sources in and out by building abstracted and normalized engines. There are two types of engines, both which are shown within this project:
Currently, the supported data sources are:
Note: This project is built to run in development mode for demo purposes. I haven't tested the build and deploy processes.
To run the project, start the Next server:
$ npm run dev
And then visit your browser at localhost:3000.
See below for working with the various data engines and their drivers (i.e. sources).
There are a series of environment variables that are required to work with various data sources:
|Data Source||Required Environment Variables||Notes|
||Local absolute path to Bear's SQLite database.|
||Notes are filtered by tag. This is the name of the tag without the
||This is a word you control when creating the content type. Usually, if the type is called
||Create an app to generate a token.|
||Sandwich files are filtered by directory. The path to the directory in which your files are stored should begin with a slash (e.g.
||The items are pulled from an index you create with Fauna. This is the name of that index.|
||Create a service account and then a JSON key. Download the key and store it as an env var, escaping quotes and other characters as necessary.|
||You can pull this from the URL when viewing the sheet.|
||You can find your API key and generate a token for your user here.|
The API-based engine example here is an Apollo GraphQL server. Its contents live in the
All drivers for this engine live in the
api-engine/lib/drivers directory and are plugged into the
api-engine/index.js entry file.
The server must be running to see it in action on the front-end. You can start the server by running:
$ node api-engine/index.js
You can then work with any of the API-based examples. You can also visit a playground for your GraphQL queries at localhost:4000.
The file-based engine has a reader and a writer. The reader is used by the front-end templates to read local markdown files. The writer pulls data from the data sources and writes them to markdown files in the
You can import files by running the appropriate command-line script:
$ npm run import:[driver]
Supported drivers are (i.e. replace
[driver] with one of the following):
If you have question regarding the implementation here or want to talk about the approach, the quickest way to get ahold of me is on Twitter: @seancdavis29.