#via using Ctrl+F to find the brackets and replacing everything with the html code

[phoenixtakaramono]

Update Status

‘The Name of the Game’ ch1 shall be posted to AO3 tomorrow Sunday 10/1/23, art and all. ✨

*I notice a considerable interest in TNotG stirring here especially (<3) and on my twitter, so I’m gonna try to post it around 9AM but no promises. Latest, check back around 3-5PM PST and it should be up on AO3! I’m excited for y’all to read it!

The Name of the Game - Ch 1 AO3 Publish Date Announcement

Since Gen V is airing on 9/29, this is a notice that chapter 1 of my 135ch QT will be posted to AO3 anytime after between 9/30-10/1. I'm currently editing the last action scene of TNotG ch1 but we're looking at approximately between 60+ to 70+ pages for the prologue itself.

Keep a lookout for it in the "Billy Butcher/The Homelander | John" tag! \(￣︶￣*\)) I'll also post here on tumblr and tweet a reminder of the official date and time before posting!

[juliaroleplays]

Some tips for HTML/CSS

Coding can be extremely frustrating sometimes, so here are a few tips that might help you figure out your problems! These tips are aimed toward people who code themes and pages, but may of them are applicable to those who like customizing their pages as well!  

Troubleshooting: 

Something not working the way it should? Always make sure that all your div tags are closed and that your declarations are separated by a semicolon and your declaration blocks are within curly brackets. Sometimes the simplest solutions are the hardest to spot. If you’re having a lot of issues, save your code and walk away for a little bit. Sometimes the solution is obvious, you just can’t see it.  

Having issues trying to figure out what part of your code is causing problems? Want to see what your page would look like without certain elements? Don’t delete your work, instead of relying on copying and pasting, comment your work in and out. Commenting your work out simply means putting this /* */ around your CSS and <!--- ---> around your HTML. Instead of manually typing, highlight the part of your code you want to comment out and hit ctrl or cmd and  / (forward slash). To comment it back in, highlight and do the same thing. This also works if you want to leave notes about what parts of the code are what parts of the theme. However, you’ll have to do it manually if you only want to do part of a line; even if you have part of a line highlighted, the whole line will be commented out. 

Trying to figure out what parts of your page are what? Go to the webpage that displays your code (on tumblr, the blog you code on for example) and right click and select inspect or hold ctrl/cmd + shift + i (for Chrome, I don’t know if it’s the same on other browsers). This will bring up the Console Panel. There will be a panel that shows you part of your code. Go to the top left and hit the button that looks like the cursor over a square or hold ctrl/cmd + shift + c (again, for Chrome). Now when your move your cursor over parts of your page. The parts you hover over will become highlighted and in the panel where your code is, the corresponding div’s will also be highlighted. This is a great tool if an element is prevent another from doing what you want it to do as this allows you to see exactly what is what. 

Can’t find a bit of coding because there’s just so much? Use ctrl + f (Windows) or cmd + f (Mac) to bring up the find feature. You can also use this to replace elements all at once by using the find and replace feature. Things like fonts and colors work best for this.   

Change something and undo doesn’t go back far enough to fix it? Consider resetting your theme via tumblr’s theme recovery page. Every time you click save on your theme, tumblr creates a back up (up to 20 saves I believe). You can see the changes between the back up and your current blog by clicking “show changes.” Just note that it lists blogs by title, not URL, so make sure you’re resetting the correct blog when doing this! And always make sure to save your current code as it will be overwritten.     

Code Organization: 

Do you hate it when you use code from someone’s tutorial/basecode and they don’t indent their lines the same way you do? To ‘reset’ the alignment of the code, highlight the parts you want to move left, then hold shift and hit tab. Hitting tab by itself will move everything you’ve selected forward, but while holding shift, it will more it back. From there you can align the code how you want. 

Other:

Don’t worry about the color before you figure things out. My pages look like the ugliest thing you’ve ever seen before I style them because I use basic colors like red, pink, black etc. for my div’s. By giving everything a unique color, it’s easier to see how elements stack on top of each other and work together. If you don’t want to look up or have to memorize a bunch of hex codes, I have a list of colors that work just by name that you can find here. 

Want to see how your page looks on other screen resolutions? Use screenfly, enter the URL and toggle between different screen resolutions to make sure your code looks good on all screen resolutions. According to W3Schools, in 2017, 84% of visitors to the site had a screen resolution of  1366x768 (15 inch laptop) or higher so keep that in mind when coding. This is also really important when making a background as well!