I generally encourage having personal websites. They have a lot of uses, and contrary to the widespread anti-self-promotion sentiment, I actually like it when someone links themselves. It gives me a way to find out what they're about if I'm interested.
So I thought I'd make a sorta guide on how to set them up aimed at people with little technical knowledge.
First, there are a lot of what I call "cookie cutter" solutions out there, like Wix and Wordpress. These aren't what I'm on about. They're a quick path to putting up some content, but they don't give you full control over the website - you're limited to what the platform offers as far as layout and style, post format, comment/account systems which are usually confusing and buggy, and anything else you might want.
This guide is gonna be about doing it "the real way" which has the following benefits:
Flexibility. Anything under the sun can be done with a server you control, not just things the platform supports.
Independence. If your website is built on a platform like the above, migrating off it will be difficult. You can probably export all your text content, but putting your website back up with a different solution would take a lot of manual work and it'd probably never be the same; especially things like user accounts or comments wouldn't carry over easily. If you self-manage your website like I do, you could set it up on a new server in an hour. I even scripted my install process so I wouldn't have to do hardly anything. That's impossible with a cookie cutter platform.
So what I'm getting at here is, the quick and easy path leads to the dark side :P
So there are a few core components that go into a website:
A domain name - the part like
yujiri.xyz. See this wonderful explanation of the Domain Name System if you're not familiar. You'll need the nameserver for the TLD (top-level domain) to resolve requests for your domain. This does cost money, but almost nothing (I get mine from Namecheap for like $13/year).
A computer to act as a server. It's actually possible to just use a home computer for this, but not necessarily a good idea because it means your website goes down whenever your internet does. Your connection may also be too slow to give a good experience to people accessing your website from around the world.
The easiest way to get a server that avoids those problems is to rent one from a service like Digital Ocean or Amazon EC2. It also costs very little (I get mine from Digital Ocean for $5/month). Note that these don't give you a Remote Desktop Connection-like interface to your server (although I'm sure there are ways to set up something like that), only SSH access. If you don't know what that is but aren't scared off by it, my Unix tutorial track can probably help - the server will be running an open-source Unix-like operating system. Do be aware that you can use SSH from Windows with PuTTY.
A web server program to run on the serving machine. I use Nginx for this; its configuration is relatively simple (it can do with just a small text file that's mostly default settings) and it supports modern protocols like HTTP 2.0 out of the box.
Something that's not required but that you should get as soon as possible is an HTTPS certificate, so users can connect securely and know that they're connected to the right website. (Sites without HTTPS support are also penalized in Google search results.) These used to be expensive, but nowadays you can get one from Letsencrypt for free with their Certbot utility.
It's possible to just write a plain text file and have Nginx or another web server program serve it. That wouldn't be very interesting though, because plain text doesn't allow for any kind of layout, style or formatting - not even things like italics. For real web content, there are three core technologies involved:
HTML (HyperText Markup Language) is what the actual content of web pages is written in. HTML is pretty easy to learn, especially since you only need to know a small subset of it unless you make spiffy web apps or something. It's worth learning even if you don't hand-write all your content in HTML, since it helps you understand how they work; it's also useful because many websites' comment systems (Wordpress and Disqus) offer HTML formatting. HTMLDog has an excellent tutorial.
CSS (Cascading Style Sheets) is how the appearance of a page is defined. CSS isn't something you use regularly though; for a blog you probably just need one CSS file that's used on every page. HTMLDog also has an excellent CSS tutorial.
Markdown - not a core technology, but it's a more human-readable language that's meant to be converted to HTML by a markdown processor, so you don't have to write all your HTML manually. Markdown supports formatting like italics, bold, headings, links, and even images with an intuitive syntax. For example, you make something italics by putting asterisks around it. Of course markdown doesn't offer the full flexibility of HTML, and it requires running the markdown processor on the text before giving it to Nginx, but it can work alongside HTML (I write my pages in markdown but I can still put manual HTML in them when I need something markdown can't do).
My implementation's open source and up for copying, though.
That's all the ingredients to a website. If you're a non-programmer following this and get stuck, feel free to ask me.