Project DART

DART.RissResearch.com is currently testing the BLUDIT CMS

Welcome to DART

the Develop And Release Toolkit

Here is the short list for use in the Core module (and also the main DART website).

CMS Link JSON API Online Edit Templates CLI Needed Multiple Logins Nonpublic Content Zipped Size Issues Annoyances Notes
Bludit Plugin WYSIWYG Markdown No? No Yes 1.6M No warning when leaving the editor without saving. If the editor sits for too long, saving brings you to the login screen without saving. Plugin adds API to the Web UI
FlexType REST WYSIWYG Markdown Forms? Fieldsets? No Yes 3.4M Existing links don't show in the editor. (they show as regular text) I'm not sure how to edit them; only insert new ones.
HTMLy Yes WYSIWYG Markdown Yes? .ini file for each user Yes login? 1.5M Links are resolved by the base CMS not HTMLy Can not find API Docs

Super small. These may have a place as an embedded tool.

CMS Link JSON API Online Edit Templates CLI Needed Multiple Logins Nonpublic Content Zipped Size Issues Annoyances Notes
FlatPress No BBCode Markdown No? No No 852K
Pico No Plugin Twig Create/Edit Files/Dirs No 820K
Singularity No No No? Create/Edit Files/Dirs No 16K 40 lines of PHP wrapped around Strapdown.js
WonderCMS No In-Line Sort-of Make Templates? No admin? 25K Long pause at 1st login of the day
Yellow No Markdown Layouts? New Layouts? No 296K Install for CMS, Wiki, or Blog

Here are the rest that are ready to look at.

CMS Link JSON API Online Edit CLI Needed Templates

Multiple Logins

Nonpublic Content Zipped Size Issues Annoyances Notes
Automad Headless 2.6M API or UI - Not Both
GetSimple DevAPI 1.3M API only for plugin development
Grav Plugin? Plugin Create/Edit Files/Dirs admin? 10.4M A beast: 10 Meg + dozens of Themes & hundreds of Plugins
Typesetter No 4.1M

We were unable to get this last group working under the same single instance of Lighttpd. (The above projects are all running under the same instance of Lighttpd, but have their own URL subsection & their own directory outside of the web doc root.) We will still give them a look, so we will install them as they were intended to be used (as a single CMS per web server, in the document root of the webserver's file system, and at the root of the URL).

CMS Link JSON API Online Edit CLI Needed Templates

Multiple Logins

Nonpublic Content Zipped Size Issues Annoyances Notes
Mecha No 90K no css
Parvula REST 1.5M 'no VIEW' error in Admin
PhileCMS 510K links not working


These links all go to a functioning CMS in the demo area. They will remain functional for testing. Periodic backups are made, so if one get too messed up, we can roll it back to a functioning state. Do not assume that anything you put into one of these projects will get backed up. Several people are testing these projects, and you will probably step on each others toes at some point.

As we learn the different packages, clean installations will be set up at the following sites. The purpose of these installations will be to see if a given project is a good fit for the production site at that link.

Domain / Site www cdn wiki blog
rissresearch.com
tweedman.com
chewymetal.com
dart101.org
vega101.org
omni101.org