![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Tutorial: Navstrips and You.
Jul. 14th, 2014 04:48 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ruriairDreamwidth just did a thing which included messing with the navigation strip to make things more mobile-friendly.
I've noticed that a few people have been having issues with it as seen here and here.
The navstrip is a table, not a div. For some reason some designers set the navstrip's table cells ("td" or "table data") to have a background color and not the table itself to have a background color. Hence you see colored cells on top of the navstrip's default light gray or dark gray gradient now where before, the colors hid the gradient due to the way the navstrip had been coded by Dreamwidth staff.
( Read more... )
I've noticed that a few people have been having issues with it as seen here and here.
The navstrip is a table, not a div. For some reason some designers set the navstrip's table cells ("td" or "table data") to have a background color and not the table itself to have a background color. Hence you see colored cells on top of the navstrip's default light gray or dark gray gradient now where before, the colors hid the gradient due to the way the navstrip had been coded by Dreamwidth staff.
( Read more... )
Tutorial: How to style icon pages.
Feb. 26th, 2013 06:33 pmruriairI'm moving this over here from my main account.
This guide is assuming you already know some basic CSS or have a concept of how it works.
.element {
property: stuff;
}
or
#element {
property: stuff;
}
Therefore you should know to always put a semicolon after each property and to close your damn code FOR EACH SEPARATE ELEMENT with a bracket. >| See also: Milou's much better guide on LJ. It shows how to do a lot of fancy tricks.
( Follow me pls... )
Comment if you have questions and I might be able to assist. (◡﹏◡✿) Comments disabled until I revamp it. If you really need help, private message me.
This guide is assuming you already know some basic CSS or have a concept of how it works.
property: stuff;
}
or
#element {
property: stuff;
}
Therefore you should know to always put a semicolon after each property and to close your damn code FOR EACH SEPARATE ELEMENT with a bracket. >| See also: Milou's much better guide on LJ. It shows how to do a lot of fancy tricks.
( Follow me pls... )
FAQ aka "Pay attention folks!"
Feb. 5th, 2013 07:28 pmruriairSomething with a layout isn't working right!
Make sure you followed each step listed. After that, check to see if I've updated the code since you copied it from its post. If not, leave a comment on the layout's specific post describing the issue.
Do you want credit?
It would be appreciated, especially for codes. Don't remove the credit from the layout CSS itself, at least, and never claim the codes or icons are yours.
May I edit your codes if I don't like something?
Yes. If you think something works in principle but is fugly in execution, do what you want.
May I repost your codes, edited or otherwise, on my blog, in a community, or on another site? Even if I credit you?
No.
( Read more... )
Make sure you followed each step listed. After that, check to see if I've updated the code since you copied it from its post. If not, leave a comment on the layout's specific post describing the issue.
Do you want credit?
It would be appreciated, especially for codes. Don't remove the credit from the layout CSS itself, at least, and never claim the codes or icons are yours.
May I edit your codes if I don't like something?
Yes. If you think something works in principle but is fugly in execution, do what you want.
May I repost your codes, edited or otherwise, on my blog, in a community, or on another site? Even if I credit you?
No.
( Read more... )
