paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 873df63432b375658ca1a3f5f9dba1b7ae8cc7b4
parent 2c6d1a59bb784b9a31ca8acf4f88f9c7f7930965
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Tue, 14 May 2019 22:01:48 -0400

Update about-site content

Diffstat:
Mpages/about-site.md | 47+++++++++++++++++++++++++++--------------------
1 file changed, 27 insertions(+), 20 deletions(-)

diff --git a/pages/about-site.md b/pages/about-site.md @@ -8,14 +8,6 @@ I created this website as a place for me to share my projects, thoughts on various computing and computer science topics, configuration files, tips and tricks, and other things that I think others could find useful. -I designed this website with the principles of minimalism and simplicity in -mind. There is no client-side JavaScript except where necessary on project -pages, the server code is contained in a single file less than 115 lines long, -and there aren't any resource-hogging images or superfluous animations to -distract you from the important stuff: the content. I took an article by Drew -DeVault [1] as inspiration for the philosophy behind the design of -this website. - The code for this website [2] is licensed under the GPL-3.0-or-later. I chose this license because of what the license stands for and what I see my website being used for. I think people should be able to audit everything about my site and @@ -42,35 +34,50 @@ have created for free and without hassle. The only thing I keep track of is how many times my pages have been visited. You can see how I do this by taking a look at the code for this website below -but it essentially just counts when a page is served and periodically saves +[2] but it essentially just counts when a page is served and periodically saves that information into a file. I do this just because I like to see what people are interested in, what things of mine have been useful, and if any pages have "gone viral" so to speak. +### Design + +I designed this website with the principles of minimalism and simplicity in +mind. There is no client-side JavaScript except where necessary on project +pages, the server code is contained in a single, small, easy-to digest file, +and there aren't any resource-hogging images or superfluous animations to +distract you from the important stuff: the content. The website has been themed +in this dark colour scheme because I found it to be easier to look at +(especially at night). I took an article by Drew DeVault [1] as inspiration for +the philosophy behind the design of this website. This site may not be flashy, +hip, or even all that pretty, but it is simple, easy to use, and fast. + ### The Technical Side -This website is built using nodejs as the back-end. This may cause some people +This website is built using Node.js as the back-end. This may cause some people to cringe, especially since this is a website serving mostly static pages, but -hear me out. I built this website using nodejs because that's the back-end that -I learned how to use in university and it's the one that I know the best and am -most comfortable with. Although in the future I will most-likely move to -Nginx/PHP for it's faster serving speeds and better database support (databases -being used in projects hosted on the site), for now nodejs seemed like the best +hear me out. I built this website using Node.js because that's the back-end +that I learned how to use in university and it's the one that I know the best +and am most comfortable with. Although in the future I may move to Nginx/PHP +for it's faster serving speeds and better database support (databases being +used in projects hosted on the site), for now Node.js seemed like the best and easiest way for me to get my website up and my stuff out there. That being said... I don't use npm. At all. Whatsoever. All of the code that -makes up my website has been written by me with help from the nodejs +makes up my website has been written by me with help from the Node.js documentation and the ever-helpful StackOverflow. There will eventually be an essay on why I dislike sub-system package managers like npm but the gist of it is that I don't like running someone else's code that I haven't fully audited, -for which I have to rely on them to maintain, and because it is way easier to -just write something like this from scratch, given the simplicity, than to try -to read and understand someone else's code. +and which could contain anything because it doesn't have to be validated by +third parties (unlike, for example, Debian packages). Also, I would have to rely +on them to maintain their packages properly. It is just way easier to write +something like this from scratch, given the simplicity, than to try to read and +understand someone else's code. The pages themselves are written in the Markdown markup language. This is then compiled into HTML, has a header and footer stuck on to it, and is released as a fully-formed HTML webpage. Because of the ease of writing in Markdown and -then being able to translate that into HTML, it just made sense to do it this way. +then being able to translate that into HTML, it just made sense to do it this +way. The CSS for the website is sent through a CSS minifier to make it as small as possible for serving to clients. The service I use is linked below [3] and is