This website can be accessed using plain HTTP or via secure HTTPS, the choice is yours. There isn't anything on here that needs HTTPS, there's no confidential data or financial transactions made through the website, and it's a bit less CPU-intensive to use HTTP. But if you feel more secure using HTTPs, there's nothing stopping you using it.
The chances are that you came here via a search engine, and it probably would have given you a HTTPS link to follow. If you typed the address in, many web browsers (now) try using HTTP, first, automatically.
Once you've connected using either of those protocols, you'll continue to browse the whole website in the same manner. I haven't forced things to work one or other the other, because there's no compelling reason to do so on my site.
I have another page going further in depth about about how forcing HTTPS is often a bit of a false security blanket. But in short: You still have to check that you're on the site you expect to be, and that a particular site isn't setting out to abuse you, HTTPS does little more than encrypt the connection, and maybe confirming the identity of the website. It is not a seal of approval.