2010-11-03, 20:39:40
Hi,
Though this is not really about the code, I would like to suggest that some sort of feature list or project definition be created, something that tells everyone what the project really is and what it is not.
I know that there is a description in the about page, and several topics around the forum talk about how GetSimple should really be simple, but I don't think anyone has ever said what is, in the project's view, simple and complex.
Take multiuser feature for instance, it is a simple and basic feature of every software that has a login. It is a basic security concern that I can create more than one account to different users. But some users think this is not in the "simple way" of the project, others feel it should be offered by the project.
This is just an example, others exist, like the contact page, why is there no core support for something as simple as a contact page that, I believe, every site in the world has, well at least the good ones .
My point is that, as a new user, I can't find any information on what the developers want for the project and what they don't want. Since I don't know what features are to be offered by the platform it's a bit hard to understand where the project will go, in the future, what I will be able to do with it, if I can go the plugin way or if I need to change to core, in which case other CMSs are a better alternative.
A simple, if I can abuse the term, list of what features the developers consider to be fundamental and what features are not considered important or needed and that should either be implemented as a plugin or be sought elsewhere. Considering that "simple" is different for everyone, listing what is "simple" for GetSimple would be a nice thing to have.
Regards,
Sérgio Lopes
Though this is not really about the code, I would like to suggest that some sort of feature list or project definition be created, something that tells everyone what the project really is and what it is not.
I know that there is a description in the about page, and several topics around the forum talk about how GetSimple should really be simple, but I don't think anyone has ever said what is, in the project's view, simple and complex.
Take multiuser feature for instance, it is a simple and basic feature of every software that has a login. It is a basic security concern that I can create more than one account to different users. But some users think this is not in the "simple way" of the project, others feel it should be offered by the project.
This is just an example, others exist, like the contact page, why is there no core support for something as simple as a contact page that, I believe, every site in the world has, well at least the good ones .
My point is that, as a new user, I can't find any information on what the developers want for the project and what they don't want. Since I don't know what features are to be offered by the platform it's a bit hard to understand where the project will go, in the future, what I will be able to do with it, if I can go the plugin way or if I need to change to core, in which case other CMSs are a better alternative.
A simple, if I can abuse the term, list of what features the developers consider to be fundamental and what features are not considered important or needed and that should either be implemented as a plugin or be sought elsewhere. Considering that "simple" is different for everyone, listing what is "simple" for GetSimple would be a nice thing to have.
Regards,
Sérgio Lopes