Does it make sense to release CMSMS modules fully styled?
Posted: Tue Jan 23, 2018 3:13 pm
Personally I never use any default module templates (or CSS that comes with a module). Either I follow the structure a CSS framework dictates or I code everything using my personal framework.
I think styling is up to the theme developer. But I like it when a module developer delivers a html prototype and documented available Smarty variables. After inserting the correct module tags I can start from there.
On the other hand I see a lot of websites with default module styling, so there is a use case for that.
What are your personal preferences and what is your opinion when it comes to module templates and styling should the module developer do this?
A.[x] Provide and overview of Smarty variables to be used inside the templates or documentation
B.[x] Provide a HTML prototype
C.[] Workout a basic HTML and CSS example
D.[] Workout awesome HTML and CSS based on a popular CSS/JavaScript framework, which one?
E.[] Workout awesome html and css without any dependencies:
F.[] Others
I think styling is up to the theme developer. But I like it when a module developer delivers a html prototype and documented available Smarty variables. After inserting the correct module tags I can start from there.
On the other hand I see a lot of websites with default module styling, so there is a use case for that.
What are your personal preferences and what is your opinion when it comes to module templates and styling should the module developer do this?
A.[x] Provide and overview of Smarty variables to be used inside the templates or documentation
B.[x] Provide a HTML prototype
C.[] Workout a basic HTML and CSS example
D.[] Workout awesome HTML and CSS based on a popular CSS/JavaScript framework, which one?
E.[] Workout awesome html and css without any dependencies:
F.[] Others