One of my standing requests with forms and pages in DIA is to have more available CSS selectors and block level elements to have full control over styling the appearance of anything and everything in a DIA hosted page to make it match our visual style and branding. As anyone knows who has ever created their own styles for DIA pages and forms, it's always been sort of hit or miss — mostly hit, but there are always a few frustrating things that didn't get a block level element and can't be styled how one might like. Old petition sigs come to mind.
This has been a pretty longstanding issue that doesn't appear to be getting better in Actions 3.0, it's actually getting worse. Or at least much more difficult to find the selectors that are there.
It's a
fairly.
recurring.
request. here on Salsa Commons. It seems every time someone mentions it, there are a bunch of "me toos!" that ring out in our lovely forum.
The two recurring workarounds are 1) Create custom pages entirely (works well with donation pages 2) use the web developer toolbar to see the code being hidden inside the javascript (never tried, but Chrome's devtools won't show it.) These suggestions might be functional, but they're really workarounds for what should be a more obvious solution:
1) Add definable CSS IDs and classes for every element on any pages (Actions 3, forms, donation pages, etc.)
2) Provide a single documentation source that lists every definable CSS element in DiA's default stylesheet and where it's used. Like a full page with some images saying "this is the textarea and this is the #textarea.content" and so forth.
At least with Actions 1.0 and other static pages, you could at least see the CSS selectors by simply viewing the source code of the page. Not everything had an class or id, but they weren't hidden in the javascript. I understand the move towards dynamic pages and content being served with JS or JSON elements, but it's making it significantly harder to find the CSS elements and find them to style them.
In Actions 3.0, some elements are picking up something applicable in the 300 lines of CSS I've written for DIA for us over the last 3 years, but others are clearly not and have the ID or CLASS hidden in Java.
So my great big recurring request is to a) add CSS elements for every piece of content on a page and b) provide a nice concise list of what they all are so we can see them. I'd be glad to help where I can. We've certainly found and defined our share of them.
Thanks!
Tagged:
Salsa,
Advocacy Campaigns