Hello (again) world
This post is out of date. I'm now using my Peppermint templating engine with Gulp for static site generation. However, though the development of this site has changed, the design section of this post is still relevant.
If you're interested in the code or concepts in this post, you can still check out the old source code here.
Since I graduated from UCSD, I have finally had time to remake my personal site, which I just launched! In this post I'll talk about the design and development decisions that I made while building it.
Working with static hosting
After I made the decision to rebuild my personal website, the first thing I had to consider was the hosting situation. I hosted the previous version of this site on GitHub, as a GitHub Pages site, and I decided that I wanted to continue with GitHub as my hosting provider because it's fast, reliable, free, and really easy to develop with. The source directory of a GitHub Pages site is just like any other repository on GitHub, which means that you can make some changes to your site, push the changes to GitHub, and they're live! Easy!
The major problem with GitHub Pages, however, is that it is a static host. There is no ability to use Node.js, PHP, ASP, or anything else that dynamic servers usually use. GitHub provides only one option to help with static site generation/templating: Jekyll. I used Jekyll for the previous version of this site and wasn't a big fan of it. That leaves me with a server that just dishes out whatever the source files are.
This is where most people would turn to a third-party library like React to do the heavy lifting for them. However, I had a strong desire not to use any third-party libaries for this project. I intended to make a nice, simple site, and I wanted to keep both the codebase and page weight as lean as possible. Additionally, I didn't want to spend a bunch of time figuring out which library or libraries to use, and then more time learning how to implement those tools. Finally, I thought it would be a fun project and good development experience for me to do everything myself. Thus, all of this site runs on my own vanilla JS.
To SPA or not to SPA
The SPA model has its advantages and disadvantages. The main disadvantage, which is the cause of several specfic pains for developers, is that a SPA is much more complex than a regular set of web pages. By limiting your site or app to a single, actual HTML page, you are unable to use several things that web browsers give you for free. The main ones are history management, link behavior, and setting the URL/value in the address bar.So, in a SPA, you have to remake all of these things, which is a substantial amount of code to write. If you instead choose to obtain these features by using a library, it can really add to your page weight. Furthermore, these replacements probably won't end up working quite as well as normal browser behavior. This is why it is often a better choice to create a website with a more traditional architecture.
Single page applications also have some pretty great benefits, such as providing a smoother, faster experience (if done well), and much better control over appearance. These benefits might be necessary to develop a webapp with a rich user interface, but they aren't necessary for most websites. At any rate, due to my host's lack of a backend to generate pages, I elected to create a SPA so that I wouldn't have to manually edit many pages or deal with static site generation, and I predicted that I could avoid some of the pitfalls of SPAs by keeping my site nice and simple.
Building a SPA
My next step was to come up with a system that would emulate the way URLs normally work—that is, a unique link for each page of content. This would make it easy for users to bookmark and share links, and search engines to index pages. In the URL pattern I created, each URL represents the path to the HTML file that contains the content on that page. This is basically the way that traditional websites are organized, which I think is a good organization for most sites. Each URL is prefixed with
index.html# (the Single Page), which is followed by the absolute path to the HTML file with the relevant content. For example, here is the link to my home page:
When index.html is downloaded by a browser, the main script checks if the URL has
#/ in it, and if it does, it uses AJAX to load the page indicated by the rest of the URL. This ensures that users can share or bookmark any page on my site without issue. It also gives me a nice way to make all my links (as in
<a> tags) look and act normally. No
Unlike many SPAs, I also took the step of trying to support users being able to open a link in a new tab by middle clicking or holding down control or the Apple command key. It works (link if you want to try), but not perfectly. There is no way to determine whether the user wants to open the new tab in the background or switch to it immediately, because that's a personal browser setting. As I said, it's hard to perfectly mimic the browser's functionality.
Managing browser history is the last main hurdle to building a working SPA. This isn't too difficult to do using
window.onpopstate. One thing to remember, though, is that you should keep track of when the user is moving through the browser history, versus making new requests.
Now I'd like to expound on some of my features and design decisions that improve the user experience. You've probably noticed some of these already. First of all, I made sure that the text is large enough and has good contrast with the background. Many designers these days fall prey to making text too small, too thin, and too light (please no more light grey text on a white background). Another important part of the user experience is speed. My page downloads are pretty small, which helps the site feel more responsive. It also helps that after
index.html initially loads, only the new content needs to be loaded.
Another of my design decisions meant to improve UX is keeping my links similar to what browsers already have by default. Many sites remove the underlines on links, but I kept them because they help distinguish links to the user. But I actually use a bottom border instead of an underline, because underlines get muddled up with letters that drop down, like g, p, and y. Example: guppy. I also have my links change on hover, to provide an additional cue to users with cursors. Finally, my links retain the default browser behavior of changing color after they've been visited. This is another thing many sites do away with, but it helps users keep track of what they've already looked at.
My favorite feature is my on-page link component. Footnotes are one place where I use this feature. There are several footnotes on this page, but here's another if you didn't look at any of the rest.
<a href="#some-content">some content<a>. One issue is that when you click the link, it's often not immediately apparent what you're supposed to be looking at. I fixed that by briefly highlighting the destination content. The other issue is that there is often no easy way to go back to what you were looking at before. So, I auto-generate a button that takes you right back to the original content. Try it!
- For this site I have a development branch and a master branch, so that I can do extended development without pushing changes until I'm ready, while maintaining the versioning and off-site backup that GitHub provides. When I am ready, I just make a pull request and merge the changes into the live version.
- Since you can change the value in the address bar without actually navigating to a different URL, such as with
history.pushState(), the value in the address bar and the URL are not always the same.
- The web was originally built for and meant for websites with individual pages, represented by individual HTML files. This model is very different from the app model, so a SPA architecture often makes more sense when you're building something more like an app than a website.
- Why hello there!
See all posts