What is this site?

This site is going to be a blog site, proof of consept and a portfolio piece.

Blog?

First of all posts won’t be constant, I am a Uni Students, this means I am very busy, I most likely do big updates every so often (like XFCE I’m busy, not dead). I am thinking of posting about HTML, CSS, JavaScript (so make a better tutorial than NeoCities, W3Schools, MDN² and other HTML/CSS/JS tutorial sites), projects I’m working on, pieces of work from Uni, Linux tips/command lists and rants about tech things. All articles will have time stamps when they were last updated, author (to make referencing easier (don’t reference me for actual essays/reports)). This is because I hate sites that don’t do this, it really annoying to have to add multiple (Anon. 20XX). I bloody hate it when these large organizations think it is ok to just not date their work or even add authors. All pages will have a PDF equivilant, I am currently using LaTeX to write these blog posts (to learn LaTeX) and then using pandoc to convert it to HTML and then I just concatinate the header and footer to it. As LaTeXis extreamly easy to convert I just though why not? Its just one command away and a few extra bytes. Finally all content, unless otherwise specified, on this site will be under Creative Commons Attributions 4.0 International License so if you want to copy, remix and distribute any content, unless otherwise specified, you can as long as you reference me, the author.

Portfolio

I am planning to make this just as easy and feature packed as most LAMP/LEMP³ News sites while being all client side. If that didn’t make any sense to you then I am going to try and implement all the features most News sites have in this site but as I am using NeoCities as a host I am unable to do anything server side. This means the site is static⁴, this is a big limitation as most News sites are very server side reliant, they use servers to implement features like: search, personalized content, comments, invasive tracking and more. This means I have to be very creative and put a lot of work in. Some of the features I am planning to implement are:

• using your Computer to search through a JSON database of pages

• using cookies and other client-side storage to store your preferences like dark mode

• using cookies and other client-side storage to remember what you have red to then recommend relevant stuff

• A JavaScript script that will search through a JSON file with tags and update links if needed

• I will embbed a different site in for comment (e.g. Discorse, Disqus, etc.)

Design

I will try to make this site look visually pleasing, unique while being simple to navigate and accessible to all (almost⁵) but i have no formal design enducation, thus I am only relying on my knowledge of CSS. I plan to have essay like blog posts so I might try to make it more that style.

One of the elements that I have already used is copying the layout of LaTeX, this means centred text, large margin⁶ and a width of 80 characters. Another thing is that I am encapilating all my text in <article> tags, this means that reading mode (in browsers taht have reading mode) will be enabled. See Figure [codeExample1] for example code. But then I might change my mind, hopefully when I have some more content I will have a better idea of what I want this site to look like.

Features

JavaScript, being the devils language⁷, is quite a powerful programming langauge but without a backend it has its limits. I want to push JavaScriptand, my abilities, to find its limit. I want to use this site to show some of the incredible things JavaScript can do on its own, I’m not going to make a WebOS like Windows93.net.

I plan on having lots of features on this site, some easy to implement, some that will take a long time. These will range from simple one liners to extreamly complex 1000+ line JS scripts.

Standards Compliance

I am planning to follow a set of standards on this web page from basic HTML guidelines to Web Content Accessiblity Guidelines (WCAG). The HTML guidelines are quite easy, it is bascially make sure that you end all your tags and stuff but the WCAG is a bit more difficult and I might even write a post about it.

Basically it is a guideline to help make the web easier for people with disability to access the web, this means that I have to do a bit more work. If your interested you can read more @W3.org.

Code quality

Now as this is going to be a portfolio piece I am going to propely comment my code, name my variables and only "use strict" JS⁸. I will also try to make tutorials on everything I do but again I am very busy so some things might not be explained, commented, complete.

Code Examples

<style>
    article{
	max-width: 80ch;
	margin-left: auto;
	margin-right: auto;
    }
    article> p, h1{
	padding-left: 1rem;
    }
</style>
<article>
    <h1>Lorem Ipsum</h1>
    <p>
	Lorem ipsum dolor sit amet.
    </p> 
</article>