Download
2011-11-24, 03:42:14
(This post was last modified: 2011-11-24, 03:51:57 by dale.c.anderson.)
Hi !
i am actually testing, GetSimple and i am still in the processes in the final choice of my CMS (between GetSimple and TemplateCMS). I have a list of suggestion and remarks for GetSimple. I hope they will be useful.
== General ==
* Add a default 'tagline' in general Website settings : Nearly all the themes i have tested use a 'tagline' component. It's already exist in the defaults components, but when i was searching for where to change it, my simple mind was looking for it in the website options.
* Add defaults meta-tags and descriptions options : Most of the time, i think of them only one time and did not change them per page basis. So i would be happy to fill them in a general section, and if i did not put nothing in the page fields, then the template would use the general ones. Actually i need cut-n-paste this on every page and my fingers don't like it.
* An 'author' fields in Pages options would be cool too : Actually the good way is to create a custom field just for it. So it's necessary to add a plugin for just this common field. It's also possible to use theme components for this but it's then site wide and not page related (some themes use this way). I can live without it as i am to lazy to do blogging, but some other people may like it along with a 'tag' one.
== Themes components ==
* Add a way to included components in distributed themes : Nearly all the themes need 'tagline' and 'sidebar' but they may not exist anymore. Alternately a few theme ask for copy-paste components after theme install. Maybe i have say this before but i am lazy. I would prefer to just install the theme files. Something like a "/components" folder in the theme witch serve as a fallback if the component did not exist would be useful. Maybe it's already easy to do this with a bit of Php in the theme files, but i do not know Php enough to do it myself. If there is not time to do this, a "missing components" warning would do the job.
== Plugins ==
* Add a dependency system in the plugin API. I do not have look inside the API, but some plugins obviously depends from others (like the I18 related plugins) but it seem to me than there i not check to see if the parent plugin is installed/activated.
* In the mean time an 'incompatible with' system and/or 'GetSimple version' check would be useful. For example "Share 5+" and "Share 3+" are said to be incompatibles in their descriptions, and it's may the case of plugins who do nearly the same thing (like the Caches plugins).
* Add a link to the support forum thread in the plugin list. Actually i need to go to GS.info to search for the plugin forum thread. I am very lazy, i would like to just clik on the support link directly from my admin page. The same goes for the themes.
== Settings and Support ==
* In the settings, please separate the "Website Settings" from the "User Profile" in two pages. Because the "User profile" stand in fact for the default admin user. So, there may be problems with the multi-user module (like an other admin change the first admin infos/pass by mistake).
* Break the "Support" button in two : "support" and "security". In this place there are basic infos, than may help basic users (Getting Started) and admin only thing like "Health Check" and "View Failed Login Attempts" log.
* Alternately, it would be good if the plugins have a directive to put their logs in this same secured place. Actually plugins logs pages can be everywhere.
== The Cache Thing ==
* By reading the documentation, it's very confusing for me to know what is the recommended way to do caching. There are plenty of concurrent plugins, an .htaccess how-to in the wiki, and a caching core feature for 3.1b explained here. I assume the last page would be the future recommended way, but she is obviously written for developers. The fact than there is not a basic cache how-to for my little lazy brain leave me a bit lost. I am not sure than it's related, but compared to the other CMS i have tested the only big drawback of GetSimple is the rendering speed (on the same host). It's probably just a cache/no-cache rendering difference, so i would appreciate a short recommended cache how-to for me
i am actually testing, GetSimple and i am still in the processes in the final choice of my CMS (between GetSimple and TemplateCMS). I have a list of suggestion and remarks for GetSimple. I hope they will be useful.
== General ==
* Add a default 'tagline' in general Website settings : Nearly all the themes i have tested use a 'tagline' component. It's already exist in the defaults components, but when i was searching for where to change it, my simple mind was looking for it in the website options.
* Add defaults meta-tags and descriptions options : Most of the time, i think of them only one time and did not change them per page basis. So i would be happy to fill them in a general section, and if i did not put nothing in the page fields, then the template would use the general ones. Actually i need cut-n-paste this on every page and my fingers don't like it.
* An 'author' fields in Pages options would be cool too : Actually the good way is to create a custom field just for it. So it's necessary to add a plugin for just this common field. It's also possible to use theme components for this but it's then site wide and not page related (some themes use this way). I can live without it as i am to lazy to do blogging, but some other people may like it along with a 'tag' one.
== Themes components ==
* Add a way to included components in distributed themes : Nearly all the themes need 'tagline' and 'sidebar' but they may not exist anymore. Alternately a few theme ask for copy-paste components after theme install. Maybe i have say this before but i am lazy. I would prefer to just install the theme files. Something like a "/components" folder in the theme witch serve as a fallback if the component did not exist would be useful. Maybe it's already easy to do this with a bit of Php in the theme files, but i do not know Php enough to do it myself. If there is not time to do this, a "missing components" warning would do the job.
== Plugins ==
* Add a dependency system in the plugin API. I do not have look inside the API, but some plugins obviously depends from others (like the I18 related plugins) but it seem to me than there i not check to see if the parent plugin is installed/activated.
* In the mean time an 'incompatible with' system and/or 'GetSimple version' check would be useful. For example "Share 5+" and "Share 3+" are said to be incompatibles in their descriptions, and it's may the case of plugins who do nearly the same thing (like the Caches plugins).
* Add a link to the support forum thread in the plugin list. Actually i need to go to GS.info to search for the plugin forum thread. I am very lazy, i would like to just clik on the support link directly from my admin page. The same goes for the themes.
== Settings and Support ==
* In the settings, please separate the "Website Settings" from the "User Profile" in two pages. Because the "User profile" stand in fact for the default admin user. So, there may be problems with the multi-user module (like an other admin change the first admin infos/pass by mistake).
* Break the "Support" button in two : "support" and "security". In this place there are basic infos, than may help basic users (Getting Started) and admin only thing like "Health Check" and "View Failed Login Attempts" log.
* Alternately, it would be good if the plugins have a directive to put their logs in this same secured place. Actually plugins logs pages can be everywhere.
== The Cache Thing ==
* By reading the documentation, it's very confusing for me to know what is the recommended way to do caching. There are plenty of concurrent plugins, an .htaccess how-to in the wiki, and a caching core feature for 3.1b explained here. I assume the last page would be the future recommended way, but she is obviously written for developers. The fact than there is not a basic cache how-to for my little lazy brain leave me a bit lost. I am not sure than it's related, but compared to the other CMS i have tested the only big drawback of GetSimple is the rendering speed (on the same host). It's probably just a cache/no-cache rendering difference, so i would appreciate a short recommended cache how-to for me
