Plan for Pluck-CMS 4.8


#1

My first plan for v4.8.

  • Move enhancements version of blog and album into core
  • New themes
  • TinyMCE v4 instead of v3 (its smaller 1,659 kb instead of 3,120 kb)

ekyo


#2

What do you think about reducing the number of requests for images?

You can also decrease the amount of request if you put all the png graphics in the admin into 1 graphic. This would speed the admin up a little. (It’s not slow by any means, but faster is faster). I didn’t do any detail analysis on how the images were used in the admin, so if I’m off base forgive me. I also know this would make it a little more work to change out images. Something to think about, I know that I’m not part of the project, but it’s just a suggestion from looking at it.

For example take a look at:

All those images - make up the images on the left side of my site www.unlocktheinbox.com

So it’s just 1 request for 1 image, instead of 27 requests to retrieve 27 images for my site.

Then in the CSS you do this, to slice up the images.

[php]span.ln-sprite {background:url(’/images/ln-sprites.png’) no-repeat top left; vertical-align: bottom;}
span#abuseicon{ background-position: 0 0; width: 20px; height: 20px; display:inline-block; }
span#non_sending_domains{ background-position: 0 0; width: 20px; height: 20px; display:inline-block; }
span#being_blacklisted{ background-position: 0 -21px; width: 20px; height: 20px; display:inline-block;}
span#email_headers{ background-position: 0 -42px; width: 20px; height: 20px; display:inline-block;}
span#email_works{ background-position: 0 -63px; width: 20px; height: 20px; display:inline-block;}
span#emailauth{ background-position: 0 -84px; width: 20px; height: 20px; display:inline-block;}
span#feedback_loops{ background-position: 0 -105px; width: 20px; height: 20px; display:inline-block;}
span#for_browsers{ background-position: 0 -126px; width: 20px; height: 20px; display:inline-block;}
span#for_clients{ background-position: 0 -147px; width: 20px; height: 20px; display:inline-block;}
span#for_devices{ background-position: 0 -168px; width: 20px; height: 20px; display:inline-block;}
span#info{ background-position: 0 -189px; width: 20px; height: 20px; display:inline-block;}
span#key{ background-position: 0 -210px; width: 20px; height: 20px; display:inline-block;}
span#lock{ background-position: 0 -231px; width: 20px; height: 20px; display:inline-block;}
span#losing_reputation{ background-position: 0 -252px; width: 20px; height: 20px; display:inline-block;}
span#mail_exchanger{ background-position: 0 -273px; width: 20px; height: 20px; display:inline-block;}
span#mail_lock{ background-position: 0 -294px; width: 20px; height: 20px; display:inline-block;}
span#mail_relay{ background-position: 0 -315px; width: 20px; height: 20px; display:inline-block;}
span#mail_send{ background-position: 0 -336px; width: 20px;height: 20px;display:inline-block;}
span#menu-down-arrow{ background-position: 0 -357px; width: 15px; height: 4px; display:inline-block;}
span#pencil_id{ background-position: 0 -362px; width: 20px; height: 20px; display:inline-block;}
span#process_bounces{ background-position: 0 -383px; width: 20px; height: 20px; display:inline-block;}
span#ptr_reverse_lookup{ background-position: 0 -404px; width: 20px; height: 20px; display:inline-block;}
span#senderid{ background-position: 0 -425px; width: 20px; height: 20px; display:inline-block;}
span#spam_filters{ background-position: 0 -446px; width: 20px; height: 20px; display:inline-block;}
span#track_clicks{ background-position: 0 -467px; width: 20px; height: 20px; display:inline-block;}
span#track_opens{ background-position: 0 -488px; width: 20px; height: 20px; display:inline-block;}
span#email_stats{ background-position: 0 -488px; width: 20px; height: 20px; display:inline-block;}
span#identifier_alignments{ background-position: 0 -508px; width: 20px; height: 20px; display:inline-block;}
span#adsp_records{ background-position: 0 -528px; width: 20px; height: 20px; display:inline-block;}
span#srs{ background-position: 0 -548px; width: 20px; height: 20px; display:inline-block;} [/php]

Then in the HTML you reference it like this, specifying the class and then the ID of the sliced graphic

[php][/php]


#3

Images - its a good idea to think about it. But as i just check - panel admin is 5 pc only (22x22px). Other images are in difrent size, 16x16, 22x22, 32x32 and even 72x72. This mean we should check all the images and images size to create a new admin image system.

Thanks for good idea.


#4

And yes, it wil be in 4.8 :slight_smile:

In 4.7.2 i want now to finish new check_applet, new pluck favicon and logo only.


#5

I’ve started editing the wiki page for planning at https://github.com/pluck-cms/pluck/wiki/Planning

Here’s what I have:

Here are some ideas for upcoming versions.
Upcoming Versions:
4.7.4 July 2015

Bugfixes
Tests
Refactoring

4.8.0 January 2016

Update the process for end users in-place updates
Choose a new default theme
Update theme for Administrator
Integrate SEO module, or include in main package

Pluck Website

Add latest posts plugin or twitter plugin
Module List
Theme List