×
Community Rules
This comm is open to anyone to post codes, layouts, resources, tutorials, and requests for help and content. Of course, we do have some rules, so please read through them before jumping in; thank you!
■
Treat others the way you'd like to be treated. This is not a drama comm, and we expect you guys to be awesome and stay civil. If a situation gets out of hand, please contact a mod, and leave comments intact so we can accurately handle the situation.
■
Please tag your posts and check out the
tagging guide if you have any questions!
■ Very long posts or posts formatted with your own div styling for organization should be behind a cut to save people's f-lists.
■
Work safe above the cut, please!
■ If posting codes, guides, etc. absolutely
do not post content that you did not make. That's stealing, and it's super uncool, bro! If you are posting expanded/edited codes made by yourself using another user's coding as well, please be sure you have their permission (You do not need direct permission if they allow edits to be re-posted in their blanket rules.)
■ Do not post tutorials/links to tutorials that show people how to steal codes from other users. Again:
Stealing. Not cool.
■
When asking for help with something, please check the help tags (
help: coding, help: graphics, help: icons, help: layouts, help: other) first to see if your question has already been posted and answered to avoid duplicates.
■
We do not allow game ads to be posted on this comm since there are so many communities specifically for that already; if you're pimping a game as an addition to a regular post, that's fine. (OK: You post an RP code and mention in the post, oh hey, also I'm running this game! NOT OK: Posts dedicated to game promo.)
■
We do allow other types of community promos if they are related to RP (icon comms, other types of resource comms, etc.) Just shoot us a comment in our dropbox beforehand and we'll let you know if it's cool to post!
Comments
I don't have a tutorial on hand, but it's pretty easy. You're basically recoding your recent entries page without touching the rest of your journal, via a .lj-view-recent .element hack. The easiest way is to set your journal entries to display only one, then code your recent entries page so that your visible entry is more or less a blank page. Full width, full height, only bare basics (like backgrounds and such) set.
So where you'd edit .entry in your CSS, you make a new section, name that to .lj-view-recent .entry; that'll affect only the recent entries view and leave your flist/day view/tags list in whatever layout you've already picked, so in the most bare-bones fashion, it should look something similar to this in an extremely, extremely simplistic form:
.lj-view-recent .entry {background:green;}
.entry {background:white;}
Doing that makes your flist/day view/etc entry backgrounds white, while your recent view has green backgrounds, if that makes sense. So what you want to do is set almost all of the view-recent elements to display:none. Do that for every element until you've cleared your elements/gotten your mostly-blank page. You want to get to the point where you can have an entry display, but that is the ONLY thing that shows and it's entirely unformatted.
Then, in your layout CSS, you'll set up the classes for your splash page. If you need a background image, it's best to set that on the .lj-view-recent .entry class. Get your classes, then code up your splash page in a forward-dated entry, and there you go.
.... and I really hope that makes any kind of sense.