Cotonti / Open Source PHP Content Management FrameworkContent Management Framework

Foren / Cotonti / Core Labs / Archive / The wishlist


The wishlist from Megamind Magazine running Cotonti

#1 26. August 2010, 18:06
No ranking of the below listed pointers. Just came up with them in this order.

1. When validating a page that has a future date set as both Date & Begin date, then it shall not appear anywhere on the "public" side of the website. But, will "pop-up" when the time and date is due. This is so that one can trigger news to be released without needing to click any button for it to release. I.e. Post future news/pages.

2. Full SEO support for Plugins with Title, Subtitle and Description support. All traffic is pulled today into pages but not in plugins like tags, search, events etc. This need to be changed.

3. More easily integration with Facebook & Twitter. Become more flexible and allow for visitors to share content.

4. Use CDN based jQuery instead of local file ( )

5. Use less javascript that is loaded in pages. 10+ javascript calls today.

6. Pull all reference to images out of the core and place them in skins. Allows for greater creativity by owners. For exemple: arrow-right.gif & arrow-left.gif that are defined in core.

These are my thoughts of things that need to be changed and improved for a even better framework. As a webmaster for a large website, these are things that need to be addressed.
Take all that money that we spend on weapons and defences each year and instead spend it feeding and clothing and educating the poor of the world, which it would many times over, not one human being excluded, and we could explore space, together, both inner and outer, forever, in peace. - Bill Hicks
#2 26. August 2010, 19:48
everything looks good except of one thing! No. 4!

I would never load external sources like that google apis in huge projects!
so i would like to see that stays in.

all other looks very well thought!
URL shortener: <a href="!7AD5C7">!7AD5C7</a>
#3 26. August 2010, 22:42
1. This could be done yes and it would make sense. Ticket #525

2. You can fully SEO for plugins. Though it may not be pretty in some cases(can't recall offhand, as i'm fairly sure it was set so all could be modified with variables)(but the developer has to do this) or you have to know how. As far as core plugins yes we should have them setup for SEO Ticket #526

3. This is a personal thing, Should only be a plugin. Sites of this nature tend to be fads and fade over time. Its really not best to put them in the core

4. Again this is something personal. The benefits are small, less bandwidth used for your server. And for client visiting sites that use it, it might be already cached for them.

5. I would not think it should be much of an issue

6 This is already done various core resources exist in system/resources.php (in the turnk)

I've added a ticket for both 1 and 2(I closed your as it was not really valid in its format)
#4 27. August 2010, 00:19
3. I wish I have time to finish my FBConnect plugin. There are also some Twitter attempts already made.

4. Cotonti works in intranets too, not only internet. We can have a CDN option though. More pros for this would be appreciated.

5. Please clarify this point.
May the Source be with you!
#5 27. August 2010, 00:35
iam against using external includes on the core system.
the system should be completly working without any external resources!!!

i.e. i load a facebook connect button on a site and somehow (sundays) the page load time slows down while the FB script is fired. letting the page load about 2 secs longer than normal. after moving all files to the core it isnt happend anymore. so i give a big bad --- for this idea! because i dont really like to modify the downloaded package everytime...

maybe there could be some sort of check-whats-the-newest-jquery-version and download it to the js/ dir on installation or in a future installation/deployment script?

Added 2 minutes later:

as for external APIs like FB connect etc. i dont really think thats good in the core.
this should be some sort of plugin...
URL shortener: <a href="!7AD5C7">!7AD5C7</a>
#6 27. August 2010, 02:18
4. The reason I would like to see a content delivery network or content distribution network (CDN) for the jQuery file is just that. If you are visiting from any other website that uses the Google libs for jQuery, then the time for loading your website is far less then if you load the jQuery script each time a visitor visits your website. Also, it's maintained and always guaranteed to be available. I have used it on my website for 8 months now and it's great.

- Take the jquery file on it weighs 55.9kb and 55.9kb is transferred.
- Google Api's jQuery file on my website (url stated above) is 70.5kb but only 24.1kb is transferred, hence smaller footprint

5. To clarify the amount of javascript's loaded when accessing a page (logged in or not) is 8 + 2 extra CSS files + 1 inline script. All are added below. I think that this could be lowered by combining and maybe even eliminating small, unessential scripts that are loaded each time you enter a page on a Cotonti based website. A smaller footprint is the basic idea that I'm after. My site as pasted below is already "slimmed" as I have stripped away access fat. Load this page on this site and take a look on how many .js .css files you can find ( ). Get my point?

<script type="text/javascript" src=""></script><script type="text/javascript" src="rc.php?uri=js/base.js"></script><script type="text/javascript" src="./images/smilies/lang/en.lang.js"></script>
<script type="text/javascript" src="./images/smilies/set.js"></script>
<script type="text/javascript" src="./plugins/markitup/js/jquery.markitup.js"></script>
<script type="text/javascript" src="./plugins/markitup/lang/en.lang.js"></script>
<script type="text/javascript" src="./plugins/markitup/js/jqModal.js"></script>
<script type="text/javascript" src="./plugins/markitup/js/set.js"></script>
<link rel="stylesheet" type="text/css" href="./plugins/markitup/skins/markitup/style.css" />
<link rel="stylesheet" type="text/css" href="./plugins/markitup/style.css" />
<script type="text/javascript">
mySettings.previewAutorefresh = true;
mySettings.previewParserPath = "plug.php?r=markitup&x=f2b4135c000be483";
mini.previewAutorefresh = true;
mini.previewParserPath = mySettings.previewParserPath;
$(document).ready(function() {
Take all that money that we spend on weapons and defences each year and instead spend it feeding and clothing and educating the poor of the world, which it would many times over, not one human being excluded, and we could explore space, together, both inner and outer, forever, in peace. - Bill Hicks
#7 27. August 2010, 04:16
4. We may have it as an option which is switched on/off in AdminCP.

5. I think this will be affected by ticket #504.
May the Source be with you!
#8 27. August 2010, 07:22
4. switch agreed!
iam off!
URL shortener: <a href="!7AD5C7">!7AD5C7</a>
#9 27. August 2010, 17:53
1. Agreed. The news plugin does this already, but it would seem logical to have it for regular pages as well.

2. SEO is a big item, I think it should be made easier to use custom titles. We have the titles section in the config, but that could use a guide or tutorial. Also I think we should look into adding extra fields to the pages for setting keywords (maybe use tags?).

3. Defenitely not for the core, but some good plugins are welcome. My Twitti is outdated (no oauth). I have built an oauth twitter client recently but it needs to be converted to a plugin.

4. Agreed. Loading jQuery from Google has its advantages. Here are 3 reasons why you should let Google host jQuery for you. Actually I think this should not be hardcoded in the core, but in the skin. That way it's easy to replace.

5. The amount of seperate files can be reduced. I was never a big fan of markitup, taking that out will take care of 6 resource calls.

6. Will be taken care of by using resources.
#10 27. August 2010, 19:26
say did you guys checked out the css / js ondemand loader from ez?
maybe this could minimize some of the js codes in the header...?
URL shortener: <a href="!7AD5C7">!7AD5C7</a>
#11 27. August 2010, 20:26
It minimizes the code but not HTTP requests which is more important.
May the Source be with you!
#12 28. August 2010, 03:14
Server-side concatenation of JS files would reduce HTTP requests. Shouldn't be too hard to make a script for that.
#13 28. August 2010, 21:31
but wouldnt it reduce also the load if some scripts are not needed they dont get loaded, so reducing the http requests... ?
URL shortener: <a href="!7AD5C7">!7AD5C7</a>
#14 29. August 2010, 21:47
I am on a holiyday with a shitty connection over here..
If interested in my rloader project, see:

I agree that we have to reduce the number of http requests..

The way to go:
1) Combining js files is the first option to reduce the # js files.
2) Loading js and css files on demand (when they are truly needed) that's the second option.

See: for some interesting reading about performance and some testing that Yahoo did.
Basically nr 1 in the list is: reduce the number of requests !!!!!

back soon.. Then me and urlkiller will start coding the pfs :)
==- I say: Keep it EZ -==
#15 31. August 2010, 03:37
Just off the top of my head - 1. - if you enable XMLRPC posting you can utilize an enormous (even freeware) number of applications that will allow you to remotely post and schedule posting in advance.
<a href="">Surreal Art</a>