Universal styles in addons? or Vanilla styles?

Permalink
I am constantly having to edit addon's to style them like my design, are there any 'universal styles' that the marketplace designated, or could the core team suggest some that people should use, i.e. i'm already styling H1,H2,h3,h4,h5,h6,p,ul,ol etc... why can't people building addons only use these styles for all instances of text?

Would there be any scope for offering non-styled addons? i.e. i often don't like the way that people design their addons and have to redesign the by removing all the existing css and tags to just get back to the basic code that I can then add tags around to style like the rest of my site. Which then causes issues on updates.

Your thoughts? Thanks

Ben

BHWW
 
LucasAnderson replied on at Permalink Reply
LucasAnderson
In my opinion this is dependent of what type of add-on and the overall style of the site it's going on, but I would agree that you should be able to re-style them easily.

I'm sure you've noticed you can create custom templates for blocks (to make them fit into your site's theme better), and this should usually be the case with purchased add-ons as well.

As an add-on developer, I try not to override the site's theme CSS if not necessary, so in my opinion the "vanilla" style should really just inherit the site's theme styles.
BHWW replied on at Permalink Reply
BHWW
Hi Lucas

I haven't bought any of your addons yet, but in general i'd say people tend to use a lot of spans and styles with unique classes, along with tables and divs in excess where not required to build a style.

I tend to use between 5-15 different custom templates per site to achieve interesting solutions, but to do this I first have to work out what code is doing the work and what code is superfluous.
ScottC replied on at Permalink Reply
ScottC
You can actually take your block views you are editing and move them to blocks/block_name/view.php, view.css and view.js, if you upgrade the package, it won't overwrite these files, though you might be missing some functionality(say the controller is providing more data to your block views, your "older" view.php might not have the correct $variable or foreach of an array, etc.

I think this is more of a documentation issue than anything else, though I totally understand where you are coming from.
BHWW replied on at Permalink Reply
BHWW
Hi Scott, yeah, indeed custom templates make C5 super flexible, but you do have to degrade the template to the primary code to really style it.