The entire framework will run on two main technologies: JSON Schema and Twig.
Directory Structure
site
parameters.json
pages
home
content.schema.json
content.json
meta.json
config
config.json
parameters.json
parameters.schema.json
meta.schema.json
templates
pages
home.twig
public
css
js
images
api
send-contact-email.php
index.php
lib
DornCMS
config.schema.json
Configuration
site parameters
The user can make a config/parameters.schema.json file that will drive an editor on the admin page for changing site-wide parameters. The editor will save to site/parameters.json.
This may contain things like:
business name
contact email
meta info
The user can make a config/meta.schema.json file that will drive an editor for each page's meta data. The editors will save to site/pages/PAGE_NAME/meta.json.
The meta.json files may contain things like:
title
keywords
description
pages
Each page needs a content.schema.json file that will drive an editor for the page content. The editor will save to site/pages/PAGE_NAME/content.json.
Administration
The user can log into the back-end with the user info defined in config/config.json. There will be a default user of admin.
Here, the user can:
edit config/config.json
edit site/parameters.json
edit templates
edit page content and meta info
Edit config.json
This will use JSON editor
lib/DornCMS/config.schema.json will drive an editor for site configuration data. The editor will save to config/config.json.
config/config.json will include:
path aliases
user logins
server info?
cache settings
Edit parameters.json
This will use JSON editor
Edit Templates
This will be a simple file browser in the templates directory and Ace editor (or something similar) for editing the twig files.
Edit Pages
The meta.json and content.json files for each page will use JSON editor.
The entire framework will run on two main technologies: JSON Schema and Twig.
Directory Structure
Configuration
site parameters
The user can make a
config/parameters.schema.json
file that will drive an editor on the admin page for changing site-wide parameters. The editor will save tosite/parameters.json
.This may contain things like:
meta info
The user can make a
config/meta.schema.json
file that will drive an editor for each page's meta data. The editors will save tosite/pages/PAGE_NAME/meta.json
.The
meta.json
files may contain things like:pages
Each page needs a
content.schema.json
file that will drive an editor for the page content. The editor will save tosite/pages/PAGE_NAME/content.json
.Administration
The user can log into the back-end with the user info defined in
config/config.json
. There will be a default user ofadmin
.Here, the user can:
config/config.json
site/parameters.json
Edit config.json
This will use JSON editor
lib/DornCMS/config.schema.json
will drive an editor for site configuration data. The editor will save toconfig/config.json
.config/config.json
will include:Edit parameters.json
This will use JSON editor
Edit Templates
This will be a simple file browser in the
templates
directory and Ace editor (or something similar) for editing the twig files.Edit Pages
The
meta.json
andcontent.json
files for each page will use JSON editor.