Architecture overview?

[riverfr0zen]

*Just* found Pligg, and it looks promising from the outside. Haven't had a chance to download the source yet, but had a few questions.

Is there an overview of the Pligg architecture somewhere? An overview with such details as development philosophy, design patterns used, and any sub-frameworks/libraries used (e.g. Smarty, Symfony) would be very useful to developers taking a first look, as it would indicate in a meaningful way what development using Pligg is like.

I searched around in the forums, and took a look at the Wiki but I couldn't find anything. Any pointers? Thanks.

[renep]

I'm new to Pligg as well, but I already feel I can answer this question "Architecture" is a big word for this application of small~moderate size and complexity.

Pligg consists of PHP code, Smarty templates and a MySQL database. It has pluggable modules, user-selectable themes (consisting of templates, stylesheets and images) and seperate files with most of the fixed texts that can be translated. Other than that, it's pretty much straightforward SQL, constructed in PHP. Oh, and there's a little Ajax in the config module

It's easy to modify, but my first impression is that modifications will be hard to maintain when upgrading to a future release of Pligg

[AshDigg]

How would you make it better? We're open to suggestions.

[renep]

Originally Posted by AshDigg

How would you make it better? We're open to suggestions.

Thank you very much. I'll post my suggestions in separate threads in the suggestions forum. My first suggestion is to make translations more maintainable.