You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CSS is joyride is making too many assumptions about look and feel, which makes it difficult to integrate into other projects. Setting the font-family is a good example of this. Implementors can either remove the CSS completely, which is tricky because the layout is part of the functionality, or override all the look-and-feel properties in another stylesheet, which is wasteful.
I think the best solution would be to split the CSS into two files, base.css and theme.css, following SMACSS conventions
The text was updated successfully, but these errors were encountered:
I am making some major changes to separate styles from the javascript functionality in Joyride 3.0. You can track these changes on the v3 branch. The new structure will be more like Foundation and follow SMACSS conventions.
The CSS is joyride is making too many assumptions about look and feel, which makes it difficult to integrate into other projects. Setting the font-family is a good example of this. Implementors can either remove the CSS completely, which is tricky because the layout is part of the functionality, or override all the look-and-feel properties in another stylesheet, which is wasteful.
I think the best solution would be to split the CSS into two files, base.css and theme.css, following SMACSS conventions
The text was updated successfully, but these errors were encountered: