First of all i want to mention that Stackideas team is top notch. This is the BEST support i ever got in Joomla "world" of paid extensions.
The products are well thought to work together but having some small "things" that can create some headache for users that are looking to obtain a customized product.
I am making this post just for an honest opinion based on my experience so far. I love the team, the support and the products ... but honestly i also had moments of frustrations
Awesome products are built based on sincere users feedback ... so here is mine
So, here we go ...
1. Assets and dependencies
Load and use as minimum "assets" (js,frameworks,css and so on) as possible into components, optimize those .... and if possible, give us the option to "iterate" product "versions" and "flavors".
What i mean by this is something like if turn off a feature .... this should turn off everything related to it.
Why to load all "groups" related stuff (css,javascript and so on) .... if "groups" are turned off in configs ?
I know is not an easy thing to do .... but i am expressing a perfect, wonderfull, "holy grail" scenario
I want my generated source code clean, with only the stuff i use.
Having to load awfull MB for just basic core assets (js and css), even if we don't use them, it's not the best thing to do.
2. Products architecture
Product architecture should be somehow separated from the design. Make the "engine" flexible enough and in such way that my "car" can accomodate different body work, different doors, shape and windows
Many times while trying to override and customize theme files i hit functionality conflict ... for only reason that i changed some div classes and javascripts started to collapse.
"Design" should be separated from "functionality", from "inner veins" of the code that provide this functionality, Mainly i am reffering to frontend design and javascripts that bring this design to life.
If you apply your javascripts to a certain HTML structure, a certain div classes and so on .... it's basically almost impossible to customize the design (without of course, tons of coffee, sleepless nights and some level of frustration)
3. Variables and their output.
If you build modules .... build them in such a way that they accomodate all variables and informations from the "core" component.
Not once i tried to output some information in a module, using a "default" code that works in the component theme file ... but in the module i hit errors, conflicts, white pages .... or simply no output at all.
For example, if i use the code that you implemented in a theme file to output "views count" ... this code should work in module theme files aswell.
Give modules the oportunity to use the entire component data, not just "trimmed" down informations with customized module variables, helpers and so on .....
More than that ....
Make variables available "cross-theme-files" . For example, often i encounter a scenario where a code used in one easysocial theme file .. will not work in another easysocial theme file (same "inner" easysocial "environment")
If i will try to output user avatar using the default code used in profile "header" theme file, in some other place, for example profile stream theme file ... it will not work.
4. Documentation
I know you guys have a lot of work with current development and support. But during "breaks" take some time to fill out the documentation aswell.
Give documentations more "juice" ... this way we don't have to come back to you and "exploit" your kind support wich, again, is THE BEST ! .... and i personally THANK YOU ! for it.
That's it for now !
if others are willing to contribute to this topic, feel free to do it
PS: I still love you !
The products are well thought to work together but having some small "things" that can create some headache for users that are looking to obtain a customized product.
I am making this post just for an honest opinion based on my experience so far. I love the team, the support and the products ... but honestly i also had moments of frustrations
Awesome products are built based on sincere users feedback ... so here is mine
So, here we go ...
1. Assets and dependencies
Load and use as minimum "assets" (js,frameworks,css and so on) as possible into components, optimize those .... and if possible, give us the option to "iterate" product "versions" and "flavors".
What i mean by this is something like if turn off a feature .... this should turn off everything related to it.
Why to load all "groups" related stuff (css,javascript and so on) .... if "groups" are turned off in configs ?
I know is not an easy thing to do .... but i am expressing a perfect, wonderfull, "holy grail" scenario
I want my generated source code clean, with only the stuff i use.
Having to load awfull MB for just basic core assets (js and css), even if we don't use them, it's not the best thing to do.
2. Products architecture
Product architecture should be somehow separated from the design. Make the "engine" flexible enough and in such way that my "car" can accomodate different body work, different doors, shape and windows
Many times while trying to override and customize theme files i hit functionality conflict ... for only reason that i changed some div classes and javascripts started to collapse.
"Design" should be separated from "functionality", from "inner veins" of the code that provide this functionality, Mainly i am reffering to frontend design and javascripts that bring this design to life.
If you apply your javascripts to a certain HTML structure, a certain div classes and so on .... it's basically almost impossible to customize the design (without of course, tons of coffee, sleepless nights and some level of frustration)
3. Variables and their output.
If you build modules .... build them in such a way that they accomodate all variables and informations from the "core" component.
Not once i tried to output some information in a module, using a "default" code that works in the component theme file ... but in the module i hit errors, conflicts, white pages .... or simply no output at all.
For example, if i use the code that you implemented in a theme file to output "views count" ... this code should work in module theme files aswell.
Give modules the oportunity to use the entire component data, not just "trimmed" down informations with customized module variables, helpers and so on .....
More than that ....
Make variables available "cross-theme-files" . For example, often i encounter a scenario where a code used in one easysocial theme file .. will not work in another easysocial theme file (same "inner" easysocial "environment")
If i will try to output user avatar using the default code used in profile "header" theme file, in some other place, for example profile stream theme file ... it will not work.
4. Documentation
I know you guys have a lot of work with current development and support. But during "breaks" take some time to fill out the documentation aswell.
Give documentations more "juice" ... this way we don't have to come back to you and "exploit" your kind support wich, again, is THE BEST ! .... and i personally THANK YOU ! for it.
That's it for now !
if others are willing to contribute to this topic, feel free to do it
PS: I still love you !