Actually, I am working through converting MODx to use sqlite.
Susan, could you progress in this project?
Instead of porting all MODx Evolution to sqlite, I dream of the possibility attaching sqlite database files through links in the MODx tree
. Anyone else interested?
The sqlite files would contain subtrees and the MODx tree as well as snippets like Wayfinder / Ditto would treat the ressources stored in the sqlite databases exactly like regular ressources in the MySQL database.
This way, you would only have to drag & drop an updated sqlite database to update all the content of a subtree. Some special icon would show which ressource links an sqlite database.
I have no idea about how difficult it would to adapt the document tree, Wayfinder, Ditto and DocManager for this. I assume that at the beginning it would be easier to disable some features, making for instance the sqlite subnodes read-only.
Another question is if the sqlite documents should have all columns of modx_site_content or if MODx could adapt to minimalist mandatory columns (id & title) and how it would treat optional non-MODx columns.
Also, for many projects, fields like "introtext", "longtitle" and even "content" are useless and sometimes boring.
For me,all these questions leads in the direction of a "MODx Evo Lite", which would become even more a generic "node management system" than a "document management system".