Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Nicereddy

  1. I shouldn't respond to this topic without first consulting Soeb, but I've done stupider things without pissing him off too much :P Soeb would be in charge of moving PCGamingWiki over to HTTPS, which is not an easy task if you haven't planned for it since the beginning (which we haven't). Plenty of large companies with paid employees have written at length about the struggles of moving over to HTTPS, so I don't expect we'll be able to do it without at least some friction. I've personally been nagging Soeb to add HTTPS to the wiki for a couple months, but there are a few things blocking us from moving over to it. The biggest problems with supporting HTTPS at present: We can't afford to become SSL certified right now, this will change at some point this year when Let's Encrypt becomes available, but probably not until then. There are some fairly cheap certification authorities available, but they're all sketchy and may not certify HTTPS compatibility properly. We cannot include third party scripts if they don't support HTTPS themselves. As far as I know, we only use AdSense for ads, which supports HTTPS, and Soeb and I have decided to remove the social buttons in the header so those won't be a problem either. MediaWiki supports HTTPS pretty well, so hopefully that won't be a problem either. I'm sure there will be something I'm not thinking of that will cause problems when we do transition to HTTPS, because there always is. IPBoard. Not sure if our forums/blog software will cause problems with HTTPS, but it definitely could. So yes, it will happen (hopefully this year), but not for another few months. I use HTTPS Everywhere myself, and I'm one of the more passionate people you'll meet regarding government surveillance. Thank you for your support via Patreon, and thank you for your concerns, you are definitely not alone in having them.
  2. We are very nearly done with the article pages now! Mobile works infinitely better than it used to, but it still needs a proper navigation bar (I'll get around to that soon-ish). I've begun work on the home page today, got the main header done (mostly, Search doesn't show suggestions): http://dev.pcgamingwiki.com/wiki/Home
  3. Also, should we call it an "Editing Guide" or "Style Guide"?
  4. I'll probably base the landing page off of the Codrops CSS reference. I would personally suggest splitting the page into various different sections for each content section (e.g. Video Settings, Audio Settings, Infobox, Input Settings, System Requirements, etc.) and then offering two means of navigation: * The current full page design, with each separate content section transcluded into the page so they'll always be updated simultaneously. * Separate pages with a "< Prev"/"Next >" design (I can handle the logistics of that if you'd like) I suggest this primarily because the page is pretty large at the moment, and if someone wants to just see the guide for Video settings, they have to wait for everything to load and then find the section. With a central page like the CSS reference linked above, editors only need to load one small page with a list of the different sections (each linking to their respective guide pages) as well as a link at the top to the "Full Editing Guide" which would essentially just be the current editing guide as it is now. Hopefully that would appease everyone?
  5. Adding on to the above, the Home page will also be rebuilt from the ground up. Hopefully loading a lot faster than the current home page by relying less on external scripts (twitter, YouTube, IPBoard). EDIT: Also we made it sort of work on mobile!
  6. Okay, so the site somewhat works on mobile now and a lot of bugs have been fixed. Anyone want to test it and tell me what I've ballsed up?
  7. Alternatively you can quit being a pleb and use OS X!
  8. I really like the tabbed system requirements table idea, so I'll keep pestering Soeb about that one ;) As for the border, I personally like the drop shadow from a stylistic perspective, and I think it has enough contrast to be able to differentiate. I can increase the darkness of the drop shadow if you think that'd help, but I'm going to be a bit stubborn about changing it unless there are any other alternatives besides the border.
  9. And here are two more screenshots so you can see the other changes:
  10. Here's our current progress, thanks to Soeb for refactoring the way all our tables work I spent a couple hours redesigning them :D [compimg]https://i.imgur.com/aO7xocm.png|https://i.imgur.com/53sGz2x.png|800|450|Before|After[/compimg]
  11. Unfortunately I can't test this very well since Windows renders text differently from OS X, but I've applied font smoothing for WebKit browsers and Firefox. I think that should fix your issue? It didn't, I'm not sure why the font rendering is all messed up on Windows :/ Considering the font we're using - Segoe UI - is the bloody typeface they used in Microsoft's logo you'd think they'd have optimized it for use with Windows.
  12. I can, I just really hate that solution.
  13. I'll have to play around some more with it then. In order to get it working the way I want, with the tag spanning the full width of the page, I need to use absolute positioning. Unfortunately, this takes it "out of the document flow", which requires I utilize extra padding <div>'s so content doesn't run under the tags. So that's why the tags aren't working the same as they were in the previous version.
  14. The font right now is Segoe UI, which I rather like. Are you seeing something different (Linux doesn't come with Segoe, AFAIK), or would you just prefer a different font?
  15. @Garrett: would it be possible to modify the way the Stub/Cleanup/Development tags work? I'm having a problem where the tags have different styles depending on what tag they are, which is rather annoying. Case in point: http://dev.pcgamingwiki.com/wiki/Grand_Theft_Auto_V Using both a Stub and Cleanup tag causes a space between the two that I can't fix without merging the templates into one single div. Something like this would be nice: {{Notice|Stub|Cleanup}} Although we should probably ask the community to make sure we get all the edge cases taken care of. I also wanted to get everyone's thoughts on using white for the stub/cleanup icons vs. keeping them as they are?
  16. @ThatOneReaper if you'd like a personal custom color scheme, I can help set up a quick little CSS template to get you going. I'm just not too keen on officially supporting them, since that'd just create more stuff to keep updated.
  17. In theory you could do it with personal CSS styles, but they wouldn't be official. I liked that when I noticed it as well. I want to add it, but I'm not sure if it'd be weird should the floating ToC happen to float over the link icon as the user hovers. Probably not a huge problem, so I'd be willing to implement it.
  18. Has anyone really been far as decided to use even go want to do look more like?

    1. RaTcHeT302


      Yes. No. Yes?

  19. After doing some initial tests, I tried loading the Half-Life 2 article on both the production and dev wikis for comparison. Note that there are a few variables that will effect this, namely advertisements (none on either since I was logged in) and the IPBoard integration on the production wiki. We currently intend to only show recent replies on the home page once we finish this up, more on that when we actually make it happen :P Anyway, here's the data: Production wiki: 90 requests, 479 KB transferred Development wiki: 47 requests, 392 KB transferred So we've managed to cut a little over 85 KB of data from the page load and almost halved the requests. In theory this should make our servers withstand larger influxes of traffic (emphasis on in theory, I am not a network engineer). I'm not sure where else we can optimize it, most of the weight is currently from the cover photo and game screenshots (my icons are all incredibly small because they're SVGs :D). I'll have to work with Soeb to see if we can get longer lasting caching of things like our logo image, etc.
  20. Here's the current version, for those interested. Very much unfinished, but feel free to give feedback. [compimg]https://i.imgur.com/7DhWqG6.png|https://i.imgur.com/a6kJqoY.png|800|450|Before|After[/compimg]
  21. I don't see any harm in supporting older systems, regardless of how niche they may be. As long as the infobox doesn't get insanely long with 8 platforms for a single game or something, I don't have a problem with it.
  • Create New...