Okay, so far, I've encountered a few problems that will certianly be encountered in the not-to-distant future. While actually getting into some preliminary coding (as available in the snapshot) I noticed that a few novel ideas will need to be unleashed to do the following things:
1. A safe, easy, and quick way to parse templates.
2. An easy, and very very obvious way to manage the navigation, to prevent confusion.
3. A more elegant way to organize and sort lots of article content, it's comments, and it's discussion... which may be spanning many many different areas of interest.
4. A way to benchmark and performance check, without having the system slow down because it's checking it's own health.
Here's a briefly written up summary of the project's goals:
The purpose of this project is to construct a flexible and robust website publication engine, with less emphasis on features, and a greater one on portability. On the user-end it should have the look and feel of an interactive magazine.
The target audience for the finished product are online publishers, as in: newspaper companies going interactive; More professional bloggers, that need self-hosting as opposed to one of the existing services; or companies with frequent news and updates that need to be published in a newsletter style.... read more
I'm currently working pretty hard to get something worthy of putting out there for people who might want to join to look at. So far, I've got a partially empty shell class and object structure. There is one template, which can be seen on the home page, which uses the engine; though, I haven't actually written the template handling class just yet, it should be done pretty soon, like hopefully by the time you read this (If anyone is reading this.)... read more