Element list for CSS customization

kevinyoung89

Smugmug doesn't seem to want to release an entire list of named elements so that we can customize elements ourselves. They want us to hunt and peck through this site. Does anyone have a list of elements?
(Perhaps we could all list what elements we know are customizable here and have it be a growing aggregate)

denisegoldberg

You can use the developer tools on Chrome or Firefox to identify the identifiers for the item you want to change.

--- Denise

leftquark

kevinyoung89 wrote: »

Smugmug doesn't seem to want to release an entire list of named elements so that we can customize elements ourselves. They want us to hunt and peck through this site. Does anyone have a list of elements?
(Perhaps we could all list what elements we know are customizable here and have it be a growing aggregate)

It's not that we don't want to release a list, it's more that the list wouldn't be very useful because the combination/hierarchy are so important. A number of elements repeat, (for example .sm-button) and its relationship in the hierarchy would let you specifically target which button. Having .sm-button listed 40 times in a document wouldn't be very useful as you'd have to go into the developer tools to figure out which one.

Chrome and Firefox (and even Safari) have developer tools, as Denise mentioned, that make it very easy to quickly identify which element you are trying to target.

If there are any specific ones you're trying to target, please do let us know and those of us here can help get you the element names.

photoclick

Aaron,

You are right and wrong at the same time. Yes, a list will not really help anyone. Combination/hierarchy dependency may be too complex for a non-technical customer.

However, majority would benefit from you providing the consistent class name for a content block that is placed on a page. Think about it. In a simplest form I drop a Photo block or similar element, I, then, drop CSS/HTML block on the SAME page and want to apply simple changes to the content block I just dropped. Hierarchy in this case is irrelevant. Why not providing something like this "sm-page-widget-10561112" right on the property page so people can see it without going to Chrome or FF development tools?

Once again - majority of your customers are non-technical. Developer tools scare them. They have no clue what they are looking for. But give them a name of a content block they just dropped - sm-page-widget-10561112 - and they can immediately write this in the CSS box on the SAME page:
"sm-page-widget-10561112 {font-size:60pt;}", right?