So I was wondering if anyone else is interested in being able to skin specific content (blog,news, article, etc) ?

At the moment the code for such things is hard coded in the pages for each content.

If anyone is interested in such a thing, post a request in this post and I will see how much interest there is and go ahead and make it possible to do.

I'd be interested in seeing that functionality.

what do you means when talk about skinned content please explain me, Thanks
Cylon

for example, you want to change the look and layout of article or category or blog or news or guide or faq, instead of having the list and the look that they currently have. Because at the moment such content layout is hardcoded into each section or category.

it will require much modification of memht core files but I can release each file with the updates already in it.

I'm planning to create a hook system for memht... What about giving the possibility to customize the look of articles, news etc, with template files? I mean, the possibility to declare in the template, how an article should look like.

Hook system sounds great, however it occurs I think that choice is a good thing so that individual sites can create something quite unique. I'm all for new features of any kind as long as they can be deactivated or not used by those who may not want to use them

I understand but if i begin to create a control panel for every single pixel of the portal you would need a dedicated server with 8 cpus to install it... a site is not a toy, you can change configuration once in 6 months, let it be 3 or even 1, but not twice a day... a content management system as first should be reliable, as second secure and third LIGHT and FAST, but those words do not get along with hundreds of controls, on off left right up down for every engine element, there must be a compromise

well i was working it this way:

for example in pages/articles/index.php, replace all the echo content fields with array value that you get from template/templatename/article_view.tpl

inside article_view.tpl you have your table or div with layout and {TITLE},{DATE}, {CONTENT} etc, then in pages/articles/index.php it loads the article_view.tpl and parses those content tags and inputs the data and show the template output.


hard to explain but I think you get the idea.

As for Hooks, yes great idea, I was alos thinking of this but it will be needed to be added to memht core because too many files to edit.

I don't think is such a problem.

Articles:


This is how a hook might work, and obviously it's not as simple as this code example, but the logic is the same

thats the stuff