Hello World - the epitome of the inaugural blog post
“Hello world!” a phrase that has been used to announce the existence of many a computer programme and blog post entry. Taking a few minutes to look into the phrase’s history today, it’s origins branch back to the early 1970s and the development of the programming language C at Bell Laboratories1 (Herbert, 2016). This sentiment of harking back to computing history seems very appropriate as I embark on the IDM18 Web Development module and reflect on my own historical coding experience. Although I have web development experience I am largely self-trained. Like many, I have learned as I have gone along and to be able to take this time to create something, in a methodical way from the ground-up is an opportunity that I relish! Thinking back to my most recent ventures into creating code and applications from scratch, the creative coding that I did in Processing (Fry & Reas, 2016) has been the closest I’ve come. It is time to up-the-ante and I want to create something that truly showcases my skills but also some of my current research interests. Ultimately this will manifest as a series of web pages, but I would like to push myself outside of my comfort zone. I will write more about my project idea here, once I have mapped it out a bit more.
How this journal will work
The posts in this journal will follow two reflective threads as I work through the module. The first thread is the development of this journal site, based on an independent install of the WordPress Content Management System or CMS (2016). I will outline my thinking behind decisions that I have take related to customisation and in particular accessibility and mobile responsiveness. These are the two key areas that I would like to learn more about during the module. The second thread is related to the creation of my portfolio website. This part of the coursework will be coded from scratch and needs to rich in features, structurally sound and accessible. More on this in a future post.
First thoughts related to this journal site
It is important to me that this journal’s theme is as accessible as possible, based on the WordPress theme templates available. At some point down the line I may even create a child-theme in order to customise it to the necessary level. For this reason I need to spend a bit of time checking the coding integrity of some of the themes that I have installed to ensure that they are suitable for customisation. I have installed a list of themes filtered for accessibility features. Please bear with me, as in these early days, it is likely that this site might change it’s skin a couple of times while I decide on a suitable theme. I will also conduct some more thorough investigations using a local copy of Wordpress and themes in MAMP (appsolute GmbH, 2016).
Provisional List of Themes for Testing:
- afterlight (Automattic, 2015)
- chuchadon (Keijonen, 2016a)
- e-nigma (Lüken, 2015)
- kuorinka (Keijonen, 2016b)
- twentyfifteen (WordPress.org, 2016b), twentysixteen (WordPress.org, 2016b) (these are default bundled themes, but I have found them to be very robust as the basis for child themes in the past and also as of March (Rietveld, 2016) they must be WCAG 2 AA compliant).
In addition, I shall run some accessibility tests on the best candidate themes using the IDI Web Accessibility checker (AChecker, 2011). As well as referring to one of my favourite sources, the BBC’s Future Media Standards and Guidelines to inform design decisions (BBC, 2008). The WordPress accessibility handbook is also an excellent resource (WordPress.org, 2014).
I have chosen to install one plugin thus far. After drafting this post and realising that I have a persistent need to include asides in my reflections, I felt that having a footnote tool was essential. Yes, it is isn’t strictly allowed in APA 6th Edition (Hume-Pratuch, 2014) but, this IS a journal rather than an essay so I think it is okay. I looked through the options and naturally chose the most frequently updated plugin with the most positive reviews. I was also looking at the plugin developers (Herndler & Cheret, 2016a) to make sure that they had a good track record and a well maintained changelog. The developers are also using a Subversion Repository for version control (Herndler & Cheret, 2016b). Based on experience I know that none of these things mean that a plugin will stand the test of time, with frequent and necessary WordPress security updates and such, however based on my assessment is seems like a robust option for the time-being.
AChecker. (2011). IDI web accessibility checker: Web accessibility checker. Retrieved October 7, 2016, from AChecker website, http://achecker.ca/checker/index.php
appsolute GmbH. (2016). MAMP & MAMP PRO. Retrieved October 7, 2016, from MAMP website, https://www.mamp.info/en/
Automattic. (2015, October 7). Afterlight. Retrieved October 7, 2016, from Wordpress.org website, https://wordpress.org/themes/afterlight/
BBC. (2008, June 24). Future media standards & guidelines - accessibility guidelines v2.0. Retrieved October 7, 2016, from BBC website, http://www.bbc.co.uk/guidelines/futuremedia/accessibility/
Fry, B., & Reas, C. (2016). Processing.Org. Retrieved October 7, 2016, from Processing Foundation website, https://processing.org/
Herbert, C. (2016, October 8). Where does “hello world” come from? [Online forum comment]. Retrieved from StackOverflow website: http://stackoverflow.com/questions/602237/where-does-hello-world-come-from
Herndler, S., & Cheret, M. (2016a). Footnotes. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/plugins/footnotes/
Herndler, S., & Cheret, M. (2016b). Footnotes (log) – WordPress Plugin repository. Retrieved November 7, 2016, from https://plugins.trac.wordpress.org/log/footnotes/
Hume-Pratuch, J. (2014, February 13). APA style Blog: Footnotes for source citations in APA style? [Blog post]. Retrieved from http://blog.apastyle.org/apastyle/2014/02/footnotes-for-source-citations-in-apa-style.html
Keijonen, S. (2016a, September 16). Chuchadon. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/themes/chuchadon/
Keijonen, S. (2016b, December 29). Kuorinka. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/themes/kuorinka/
Lüken, A. (2015, October 31). E.Nigma 2015. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/themes/e-nigma-2015/
Rietveld, R. (2016, March 21). WordPress goes WCAG [Blog post]. Retrieved from https://make.wordpress.org/accessibility/2016/03/21/wordpress-goes-wcag/
WordPress.org. (2014, October 11). Accessibility handbook. Retrieved October 7, 2016, from WordPress.org website, https://make.wordpress.org/accessibility/handbook/
WordPress. (2016a). Blog tool, publishing platform, and CMS. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/
WordPress.org. (2016b, December 6). Twenty Fifteen. Retrieved October 7, 2016, from WordPress.org website, https://wordpress.org/themes/twentyfifteen/
WordPress.org. (2016c, December 6). Twenty Sixteen. Retrieved October 7, 2016, from Wordpress.org website, https://wordpress.org/themes/twentysixteen/
There are differing opinions on the exact origins, but it was a nice introduction to developer commentary and critique on Stack Overflow! ↩︎