It’s National Reading Month, and I hope whatever it is you’re reading — a novel, memoir, blog post, dossier on a foreign diplomat — you’re enjoying it and sharing it with someone. Personally, I share books with people by leaving unmarked packages on their doorsteps. But I’m told other people prefer to share their reading lists through social media. Seems like a security risk to me, but to each her own.
If you’d like some advice on using social media, Ahna Ziegler has been sharing her expert insider tips on the Coffee Break vlog over the last few months. (She calls the video series Social Media 101. I call it How Not to Be a Spy.) Yesterday she gave some helpful intel on starting a blog.
But, of course, that’s not the whole story.
The original video we filmed contained a lot more information — the kind of technical data that you can only obtain from infiltrating certain organizations (and no, I can’t tell you which organizations — need-to-know basis and all that). However, our video editor was worried about what would happen if that data fell into the wrong hands. He won’t admit to anything, but some sections of the video were mysteriously erased from the drive. Along with our notes. And the backup files.
Naturally, Ahna and I were not going to accept this. So we held a clandestine meeting and typed up all the deleted information from memory. Then we rewarded ourselves with coffee and bagels. (Little known fact: Spies love bagels.)
As usual, what follows is top-secret information. Ahna and I put in enough security measures to ensure that they won’t discover we leaked this, but if they do ask, you didn’t get this from us.
Ok, so you’ve chosen the awesome title for your blog (and it had better not be Bloggedy Bloggy Blog; you know that’s ours) and the platform you’re using. Next, choose a theme. Our best general advice is to choose something with a recent creation date so that you know the developers are still supporting it; often the theme creators themselves can answer your CSS questions on a Blogger or WordPress forum. Once you’ve applied your theme, there are probably things you’ll want to change. This is why you will now be embarking on the incredible adventure of learning code! Welcome aboard.
Now, we won’t try to teach you everything about CSS here; that would be impossible (plus, despite what she tells Katherine, Ahna doesn’t know everything about the Internet). We will, however, try to teach you how to teach yourself CSS.
You’re all English nerds (I assume), so you just need to think of CSS as a different set of grammar rules — but even better, because there are no weird exceptions and everything has only one place to go. Diagramming sentences was awesome, right? You’re actually going to love CSS.
First, you’ll want to get familiar with what CSS looks like. CSS “rules” have “selectors” and “declarations.” W3Schools has a really great explanation of this (and of pretty much everything code):
Basically, the selector identifies the part of your blog you want to change and the declaration tells how to change it. Both of them laid out together — like a complete sentence — is called a “rule.”
Now you just need to get familiar with the language of HTML and CSS — which words to use for selectors, properties, and values. Again, w3schools can help with this, but also Google. Bonus spy tip: if you highlight a section of your webpage and right click (or control+click), then select “inspect element” (if that doesn’t show up, try using Google Chrome instead of your current browser), you can see all of the code happening behind the scenes!
I hope that data was helpful for all you potential/fellow bloggers. Now, if you’ll excuse me, I have a vault to break into a train to catch.
* * *
About Coffee Break Confidential:
This monthly column is where EBYR editorial assistant/vlogger/superspy Katherine Gibson divulges extra information from Coffee Break with EBYR that would otherwise be kept off the record. She’s researching topics related to children’s literature, posting her findings — and taking down some powerful militarized governments in the process. Just kidding about that last one. (Or are we?)