Hi and welcome to the first entry in what I’m hoping will become a series of posts detailing the creation of the very website you are currently visiting.
A while ago I started taking online courses to teach myself how to code—mainly in HTML, JavaScript and CSS—and while it’s been a great deal of fun and a good exercise in acquiring the fundamentals, I thought now was the time to use what I’d learned and try to write and upload my own website on a server somewhere. Probably in Florida. Or maybe elsewhere, what do I know?
Anyway, my site is written in Markdown syntax using plain text files and doesn’t require a content management system to run; for keeping the code readable and easy to iterate upon, entries are linked using what is called automated taxonomy collection (I swear I didn’t make that up).
Don’t we all have to start somewhere?
Right now, I’m barely getting started on the project. Current tasks include writing an index, setting up page navigation and customizing the <head> and <body> sections with specific stylesheets for tables and code blocks, such as the Prism syntax highlighter. Below is an excerpt that shows how I extended my CSS with scripts that are hosted externally.
<!-- CSS Styles -->
<link href="/assets/css/style.css" rel="stylesheet">
<link href="Prism link here" rel="stylesheet">
<!-- Javascript Assets -->
<script src="/assets/js/jquery-3.2.1.min.js"></script>
<script src="/assets/js/plugins.js"></script>
<script src="/assets/js/custom.js"></script>
<script src="Prism link here"></script>
<script src="Prism link here"></script>
Speaking of tags, I’m a big supporter of minimal tagging, meaning that a page, post or article shouldn’t be called upon by more than a handful of them. This makes page headers and feeds far easier to read and understand. And since I’m fairly new to all this, I can certainly appreciate the ability to flip through different sections like I would a printed book.
Next time I’ll get into the no-cookie policy I want to implement.
