AtF Spark is “a typeface for creating sparklines in text”. In other words, the fonts will convert numbers into something that looks like a chart. It looks pretty cool, and is a neat way to add a little spark (ahem) to your text.
But while the GitHub repo gives some basic instruction on using the fonts, it also assumes quite a bit of prior knowledge, so here’s a tutorial to explain how to use it if you’re not already familiar with web fonts and other technicalities of web design. Continue reading →
A customised car. Like a customised blog, only bigger. Image by Steve Metz - click to see original
Although I cover blogging in some depth in my online journalism book, I thought I should write a supplementary section on what happens when you decide to start customising your blog.
Specifically, I want to address 3 key languages which you are likely to encounter, what they do, and how they work.
What’s the difference? HTML, CSS, and PHP
Most blog platforms use a combination of HTML, CSS and PHP (or similar scripting language). These perform very different functions, so it saves you a lot of time and effort if you know which one you might need to customise. Here’s what those functions are:
HTML is concerned with content.
CSS is concerned with style.
And PHP is concerned with functionality.
If you want to change how your blog looks, then, you will need to customise the CSS.
If you want to change what it does, you will need to customise the PHP.
And if you want to change how content is organised or classified, then you need to change the HTML.
All 3 are interrelated: PHP will generate much of the HTML, and the CSS will style the HTML. I’ll explain more about this below.
But before I do so, it’ll help if you have 3 windows open on your computer to see how this works on your own blog. They are:
On your blog, right-click and select ‘View source‘ (or a similar option) so you can see the HTML for that page.
Open another window, log in to your blog, and find the customisation option (you may have to Google around to find out where this option is). You should be able to see a page of code.
Eric Ulken has taken “all the online job descriptions on JournalismJobs.com from this year, omitted the non-technical words (like “editor”, “seeks” and “self-starter”) and built a tagcloud out of the rest”. This is the result: