SirMoo
💖 Chevereto Fan
With the growth of Chevereto and the constant request and debate over the usefulness of features, I fear that CHV will struggle to meet the one sizes fits all approach. Features that sound good to other users seems beyond pointless to me when it comes to my usage cases of the site. Furthermore, software and database bloat is likely to occur because of this.
To avoid and prevent features that are likely to be useless to the end users, I'd love to see a more modular system. One that mimics the plug-n-play addon system of Wordpress would provide the most benefits, in my opinion over the overly feature packed concept of putting everything into the raw program.
Comments and Pay-to-Use systems to me, would be pointless and unneeded. A solution to this would be these type of plugins, while developed by Rodolfo (or who ever) be released as 'addons' to the main system and simply placed in a /addons/ folder and an installer run for database changes. I feel this is one of the critical features that sets WP apart from other programs and that Chevereto could benefit from by not having everything directly in the core code.
A modular system will allow and encourage more customization and sharing of modifications by users. I cite WP as an example because I've hated having to use systems of companies like IP.B where mods are located in a maze of public/private folders. Simplicity in modification will make Chevereto even more stronger.
Now I completely understand what a task this make be and am not expecting a massive change to the code base over night. As I understand G\ Library is being set up to accommodate a system of hooks in the program so, theoretically you're already putting in place the bones for this to happen.
Long term goals would allow for people to develop more storage and payment options as well as cacheing and other systems outside of the core using libraries. As well as having an independent non-theme based admin and less reliance on the main theme design.
Please do let me know what you think and the theoretical issues forseen with this.
To avoid and prevent features that are likely to be useless to the end users, I'd love to see a more modular system. One that mimics the plug-n-play addon system of Wordpress would provide the most benefits, in my opinion over the overly feature packed concept of putting everything into the raw program.
Comments and Pay-to-Use systems to me, would be pointless and unneeded. A solution to this would be these type of plugins, while developed by Rodolfo (or who ever) be released as 'addons' to the main system and simply placed in a /addons/ folder and an installer run for database changes. I feel this is one of the critical features that sets WP apart from other programs and that Chevereto could benefit from by not having everything directly in the core code.
A modular system will allow and encourage more customization and sharing of modifications by users. I cite WP as an example because I've hated having to use systems of companies like IP.B where mods are located in a maze of public/private folders. Simplicity in modification will make Chevereto even more stronger.
Now I completely understand what a task this make be and am not expecting a massive change to the code base over night. As I understand G\ Library is being set up to accommodate a system of hooks in the program so, theoretically you're already putting in place the bones for this to happen.
Long term goals would allow for people to develop more storage and payment options as well as cacheing and other systems outside of the core using libraries. As well as having an independent non-theme based admin and less reliance on the main theme design.
Please do let me know what you think and the theoretical issues forseen with this.