Inline Styles

Inline Styles, a forum discussion on Jojo CMS. Join us for more discussions on Inline Styles on our General Discussion forum.

Back to Forum Index : Back to General Discussion   RSS
SoulGlo

15 Oct 2009
Posts: 17

Hi Guys,

I'm looking to for my own needs strip out all the inline styles within Jojo and all its plug-ins. Is this something that anyone else would be interested in?

While I'm not a design expert I think one area that Jojo could improve is having guidelines for developers to ensure that they separate all content from the design elements and place it into an external CSS file.

If there is enough interest from others (and the Jojo developers) I'm happy to help commit the changes to the SVN.

Thoughts? Happy to discuss..

Cheers

SG
tom

Developer

tom

15 Oct 2009
Posts: 379

Sounds brilliant to me.

If the CSS can use ids or classes can be wrapped in ids where possible or are tag specific that would be great - so #cart div.totals or input.contact-checkbox

The Xinha editor allows users to use the styles in css for styling their content, but this becomes almost impossible if the styles list is clogged with generic class styles like div.message

If template elements can be more classed or id-ed while you're at it, that's helpful too (so you can use css to display:none parts of the template you don't want rather than having to do custom templates) - the other alternative is to add options into api, but, in articles for instance, the number of options has become somewhat unwieldy...
SoulGlo

15 Oct 2009
Posts: 17

Excellent - I'll get my hands on the latest core and put together a plan of attack.. and hopefully put together some guidelines for future developments.
tom

Developer

tom

15 Oct 2009
Posts: 379

For the moment.. given the extreme flux of trunk - get a copy of the 1.0 branch and use that (and commit to that branch).

We can merge changes up into trunk as they come in, but given that commits to trunk aren't likely to see the general light of day for a while, you might as well make your changes where they can be more immediately useful.

you can commit to both trunk AND branch of course.
Trunk is going to be Dwoo only - so no smarty specific tags please (like @count, section) if you're going that far with stuff and commiting to trunk.
Rick Rick

15 Oct 2009
Posts: 336

Nice idea with the removal of inline styles.

The Article options can be tidied up by making a separate options category of all of the RSS options for example. On the downside, this of course makes the list of options categories longer.
Rick Rick

15 Oct 2009
Posts: 336

Then again, I guess the categories list could become a tree...
SoulGlo

15 Oct 2009
Posts: 17

tom said...
For the moment.. given the extreme flux of trunk - get a copy of the 1.0 branch and use that (and commit to that branch).


Okie dokie - I'll grab a copy and go from there.
Back to Forum Index : Back to General Discussion   RSS
You must be logged in to post a reply



You need to Register or Log In before posting on these forums.