TechAngel85

No, not the onMouseover event. That is glitchy and horrible. But it's possible to do it entirely with CSS now. Just assign all the CSS code to a class and add the class to the container for the bar. Simple as that (assuming there is no trickery involved with the bar). The CSS way of doing it is reliable because I'm pretty sure I've done it in the past on a web site. But, Lord no, please don't use any onEvent elements!

We meant for it to be in both places.

Meta Rule Instructions SkyFalls and SkyMills should Load After Distant DetailHF.esp (this mod) That was what the mod page says for this mod. Not sure where you got what you posted from.

The H1 and H2 headers still need some work. I was experimenting on the ENB Guide because I thought it odd that the main headers were H2 tags and not H1 tags. So I changed the top two sections and this is the result: https://wiki.step-project.com/Guide:ENB Ugly! This is worth fixing and doing it right because most users are going to assume that the H1 tag is the top tier when writing wiki pages...because they're suppose to be...not H2 tags. That H1 header needs some white space above it and an underline that reaches across the width of the page like the H2 tags. The H2 tags are fine but I think the should be de-emphasized but adjusting the width of the line to only around 50% of the page. This reflects what I have done in my Mass Effect Guide to emphasize clear structure to the headings rather than simply relying on font size and weight. You can see that the H1, H2, and H3 tags all have different widths for their underline which visually structures them into a sub-section of the main section they reside in. The font size and weight changes (reduces) as normal as you go deeper into the structure (though I've customized those as well from the defaults). The only issue with changing the H1 tag in the CSS would be that I believe you guys are using that for the page title at the top. A solution to this and which would be more proper coding is to assign a class to the page titles so that nothing can interfere with them. Element Class H1.pageTile{ } or... Generic Class .pageTitle{ } Either one works but the first one would only be able to apply to H1 tags and nothing else.

https://wiki.step-project.com/Guide:ENB#ENBoost

Okay, I'll wait to see it any of the other authors comment on the new layout and any of this discussion. For now, I'll just keep the brackets when I'm editing. I have a PM out to all the author notifying them to check in when they get time.

That looks good on the main page the the other issue was the TOC on the sub-pages which was the first time I noticed that it was a bit hard to read (the reason for me removing it on the heading). It's something that I can deal it. It at least looks much better on the main page. I already had to tweak the custom CSS to work around the TOC...which I didn't know you removed until I seen some things were wonky with the compare placements their headings. Anyway, this thread heading off topic to a degree.

I don't agree. When it's all caps like the headers, readability is an issue. Otherwise, I wouldn't care either way...and at least this: SKYLIGHTING is closer to this: [sKYLIGHTING] than this: [skylighing]. Here on the forum it's okay. However, on the wiki when you add in the color and the underline for the link, it gets to be too much for the eyes imo, especially seeing them altogether. Which is easy to read? [sKYLIGHITNG] SKYLIGHTING I would say the second as it's cleaner and the same message is applied in the text....the SKYLIGHTING section. The INI Guide is not going to have anything else in it other than the INI sections themselves, so there is no possible way for it to mean anything else other than that section. I think a user to determine that within the first second of reading it. If the guys what to add stuff in about the other files, shaders, etc, then we'll add those as separate guides as they would have little to nothing to do with the ENBSeries INI file. You can copy this layout for other INI Guide. Which INI settings are you referring to in your PS?

Dreamweaver... I do all my HTML by hand. Used to find Dreamweaver very limiting. CSS: .center { margin: 0 auto; width: 600px; }HTML: <div class="center"> whatever you want centered </div>

I understand where you're coming from and getting at to make it match the INI exactly but it's just a header and a title. Whether there are brackets there or not, it still conveys the message that it is for the SKYLIGHTING section of the INI. Also, from a readability standpoint it's hard to read with the brackets. I personally like it better without the brackets and it was one of the first things I removed. Things like this doesn't need to be exact as it's just a header. [sKYLIGHTING] in the INI is just a header for the section. SKYLIGHTING is just a header that is more readable on a Guide. PS: I don't use the talk pages because there is no notification of new posts to them.

If anyone is still keeping up with this... Z has finished applying the new layout to the Guide which consists of a main page with sub-pages for each of the individual sections. It's different than most Guides; however, this was the best way to set up such a Guide with as many images as it's going to have. As for news on progress, I've finished up the Skylighting section. It will need to be checked and verified for accuracy.

Talking about the Mist settings. It was time of day parameters that could affect this just for that time frame.

I think it would be useful to have a namespace for guides that are created for other games. Right now, they're just all hosted in the user namespace of the creator. Moving these to a common namespace would increase their visibility and may encourage more.

https://drive.google.com/file/d/0B1_Nlyy2ueu0bkVacHE1SldPaVE/view?usp=sharing EDIT: Added link to OP.

There's no limit. If you need to clean something up and have page deleted from your userspace, you'll have to contact a staff member though.

I use my main user page as a collection to my personal works and ideas as well. This is becoming the normal as I think EssArrBee and DoubleYou do the same.

You need a parent div as a container and make it the width of the page and center the child div within it. Even better, use CSS to give the fix a fixed width to the div and center it on the page using margins.

Looks like fog.

S4N said the there is no need to include the Revision time stamp on the wiki pages that you've added to the guide format. The same information is already available in the grey box at that bottom of the pages where the quick search is located.

Not a game, but still a good deal. Bethesda has a deal on t-shirts that ends today: 2/$25, normally $20 each. https://store.bethsoft.com/ Looks like BioWare is having the same deal: https://www.biowarestore.com/apparel/t-shirts.html

Was browsing the wiki today and I had a thought on this matter... Is is possible to make the top bar fade in and out? An onMouseover event in HTML/Javascript used to be able to do this; however, I'm fairly positive this can be done via CSS now without the need for Javascript. This would be fairly simple to implement by just dropping the necessary code into site's CSS file and applying a class or id to the top bar's container element (as long as the child elements inherit to properties correctly). Doing this to top bar would fade out when not in use and fade in whenever it's needed and the user mouses over it.

No idea. Without a server to test on, that's about all the help I can think of to provide. The last thing I can think of is to ensure the server has the required features to run it. That's usually more of a PHP script issue (making sure the server's PHP is up-to-date), but you never know. If you can't get it perhaps attempt a different jQuery slider to see if it works or fails. If several of them fail, it's almost guaranteed a server issue and something needs to be installed, updated or allowed to run on the server.

And you're calling in your HTML like so: <div id="main"> <ul class="slideme"> <li><img src="img/one.jpg" alt="One"/></li> <li><img src="img/two.jpg" alt="Two"/></li> <li><img src="img/three.jpg" alt="Three"/></li> <li><img src="img/four.jpg" alt="Four"/></li> </ul> </div>

No idea. I don't have any way of testing and troubleshooting. I'd just say, double check to make sure you're calling it correctly in both the script and the HTML. Haven't had a web server in quite a while and in the end of my website designing days I shifted towards Wordpress. So you've tried this? <!doctype html> <html> <head> <meta charset="utf-8"> <title>Mediterranean Grille</title> <link href="stylesheet.css" rel="stylesheet" type="text/css"> <link href="nav_bar.css" rel="stylesheet" type="text/css"> <script src="jQueryAssets/jquery-1.8.3.min.js"></script> <script src="jQueryAssets/jquery.slideme-1.19.69.js"></script> <link rel="stylesheet" href="jQueryAssets/slideme.css" type="text/css" media="all"/> $(document).ready(function() { $('#main').slideme(); }); </head> <body>

According to documentation, right under the link reference element within the head: