https://www.cotonti.com Last topic posts Cotonti en Sat, 07 Feb 2026 22:54:00 -0000 Feel free to submit new Trac tickets. Most likely full HTML5 will be in Renaissance, not Siena, because there's still a lot to be done for Siena.]]> Sun, 17 Oct 2010 19:16:45 -0000
Currently I'm looking into the Cotonti CMF to see if there are things that can be submitted to TRAC, as alterations, and also what needs to be and what doesn't need to be in each tpl file as far as HTML is concerned.

Added 124 days later:

I've just released my new version of my website and it's validated HTML5 and CSS3. It's a Cotonti backbone with a HTML5 & CSS3 skin. A few backbone alterations had to be done. Mostly forms related and image output (constant problem, which is going to be fixed I'm told).

Have a look here: Megamind Magazine by aiwass]]> Tue, 15 Jun 2010 03:33:20 -0000 http://html5demos.com/

I've already built a Cotonti site with CSS3.]]> Mon, 14 Jun 2010 16:55:31 -0000 Mon, 14 Jun 2010 14:44:38 -0000
Skins for Cotonti
There should be no problem converting or creating new skins in HTML5 & CSS3 for cotonti as much of what is being parsed already is stated in .tpl files. This is more up to the designer of the site and the skill rather then Cotonti itself. However there are a few things that might not be able to convert and those being plugins that have no .tpl files or where the .tpl files are hard to design you own way (search being one standard plugin that is really hard).

Parsed from within the backbone
Yes, there are a few things that are actually "outputted" from within the Cotonti engine itself and these are the ones that might be a bit of a challenge to get right and to locate. One, that I bitterly hate, is the comment.gif that is "outputted" from within system/functions.php (line 1102), since I want to control what is shown on my website and I also want to control how it is shown. Every time Cotonti upgrades system/functions.php I have to edit the file before I upload it and replace it. Is that what I want? No, is the obvious answer and neither would you, as a designer.

There are a few more, but since this is not going to be bitching thread, but a inspiring one, I'm going to leave you with one problem instead of 15 problems.

What could be done?
Basically anything could be done. From a designers point of view the limitations are really what you set yourself as far as design goes. My belief is that the Cotonti backbone could be very good, stable and fast using HTML5 and CSS3 as the main components for skins. However there is a learning curve and it's rather steep, but rewarding when you've learned the new way of coding.

What could not be done?
This is something that I'm currently don't have the answer for, but as soon as all parts of the Cotonti backbone is HTML5 (what is "outputted" that is), I do not think that there is any problems in making good use of it.

The idea that will become a reality
I will start soon on converting and creating a fully HTML5 and CSS3 website based on Cotonti. It is actually a redesign of my current one that is also based entirely on Cotonti. The project should be finished around the end of July or early August 2010. My website is available on the left hand side.

Q & A
If you have any thoughts, ideas, questions or just curious, just drop a few comments in this thread and I'll answer them as soon as I can.]]> Sat, 12 Jun 2010 14:57:04 -0000