This is the first entry of my WordPress development series, providing tutorials on specific things you can do in WordPress. Stay tuned for more!
I have been working with Custom Post Types recently, so I want to start off the series with them. Custom Post Types are just like Pages and Posts, but you can call them whatever you like. They can be used for a variety of content such as Events, Bands, a Book database, Cars, Recipes… if you can think of it, it can probably be a Custom Post Type! They are handy because you can separate them from your regular blog Posts, they can be integrated into your themes and plugins, and even created just by using functions.php.
For simplicity, we will create our Custom Post Type in our functions.php file. You can edit this file by going to Appearance > Editor in your WordPress admin panel, or using a text editor with FTP. I’m going to be creating a post type called Cats.
Read More »
There has been a lot of discussion lately on blogs and Twitter about the use of vendor prefixes, and I’d like to add in my two-cents.
I initially came across the whole thing from Chris Coyier at Css-Tricks.com, followed by tweets from various web professionals on Twitter. Essentially, Mozilla (those behind the Firefox browser) wants to provide support for Webkit’s -webkit- prefix (that is used by browsers like Safari and Chrome that use the Webkit engine). A lot of people are saying this is a bad idea. Others are also saying we (the designers/devs) have gotten ourselves into this mess. I think it really comes down to all of us – the browser vendors, the W3C, and the web designers/devs.
The browser vendors have their own set of prefixes that they use for experimental purposes – it is pre-standardized code, and prefixes are not spec. Firefox uses -moz-, Safari and Chrome use -webkit-, Opera uses -o-, and Internet Explorer uses -ms-. Apparently, web designers/devs are using the -webkit- prefixes only, to use properties we call “CSS3”, because they either don’t know about the equivalent prefixes for other browsers, or don’t bother (sometimes, though, they don’t exist). Technically, some of these fancy schmancy techniques we use with prefixes aren’t really CSS3 – yet, anyways depending on how far along they are towards W3C recommendation. Many of these techniques are kind of like previews, and allows the browser vendors to test stuff out (as well as designers/devs too, who can provide feedback). Some browser vendors are already supporting standardized CSS3 properties. But the support varies with each browser vendor, and some browser vendors are using their prefixes to test things, and not all are testing the same things.
Read More »
As users of the web, we have to be careful with security and make sure hackers do not get into our bank accounts, emails, and our websites/blogs. Here, I outline some simple things that you can do to make sure your WordPress blog/website isn’t the next one that gets hacked.
Don’t use a simple, short password!
This is probably one of the most simplest things you can do to make sure your blog is safe. Using a combination of upper- and lower-case letters, numbers, and symbols is going to make your password harder to crack – and the more, the merrier! I would recommend using a password no shorter than 8 characters long, and try to make it as long as possible. Most websites allow long passwords, so don’t be shy!
Read More »