AlexPaes wrote:I would very much like to get some more information about this project. I've been trying to push CL into my company's development tools but they are working with an existing open-source CMS and are afraid of the change, so this project could actually drive my company to make the switch.
I think it'll be quite a while before this matures enough to displace anything already in place, but it's certainly worth aiming for - if it's worth doing at all, I may as well aim to get it right.
Where it is now: I've built, and am refining, fairly task-specific software that runs a couple of online gallery/shops. I generalise things where it looks feasible, which has produced a couple of libraries that I'm polishing for initial release.
One of the sites is for my partner who, though possessing at least as much aptitude as me, has no interest in getting into programming. I've already built functional-but-ugly admin interfaces, but now need to build the machinery needed for user-generated content in pages, blog-posts, blog comments and news articles. Plain text is easy enough, and will be the first iteration, but it'd certainly be nice to include something like BBCode... and it's at this point that it starts looking like a CMS.
So there's a good chunk of refactoring for me to do, because I'm a bit reluctant to publish the code as it is. There are a couple of big changes to be made yet: one is architectural, increasing the degree of object orientation; the other is design-related, moving from CL-WHO-based functions to HTML-TEMPLATE for the graphic design. The latter move should simplify and reduce the actual codebase significantly.
So I'm looking at releasing the initial rough version once it's become a generalised machine to which I feed config files. The nice thing about CL, of course, is that the config files themselves can be both valid CL and easy to understand and modify