Nuxt up? Get it? Next up, Nuxt, Nuxt up…? I'll see myself out.
I've once again rewritten the entire website's code. However, instead of doing everything the old-fashioned way again, I've now innovated! Yay!
The entire site is now written using the Nuxt framework. Then—because this is technically a static site—everything is compiled into plain HTML, CSS, and JavaScript files, and assets are also generated. What this means is that you should not see much change—if any. The UI remains mostly untouched apart from some minor tweaks and adjustments.
The reason I chose to remake the entire site using Nuxt is that I simply like working with Vue. The most useful feature it—but also other frameworks—offer are components They're also the main reason why I switched to Nuxt; whenever I want to change some little thing, I usually have to go and replace the code for it everywhere. With components, that's no longer an issue. The reason I chose Nuxt specifically is that I prefer Vue's handling of everything. Its structure for building a page is much simpler and much more intuitive than that of something like React.
Though, to compensate, I have changed the structure of the whole site as well. For instance, there is no longer a subdomain—at least, not officially. Instead, everything is now present under the main domain q-file.com/. The docs subdomain still exists, it just redirects everything to the new pages.
If you want to know further specifics:
- I'm using Sass for my stylesheets, specifically the superset syntax offered in
.scssfiles. I simply prefer it over things like Stylus because of Sass' minimal and simple feature set. - The site's functions are now all based entirely on TypeScript. This ensures that everything works fully as expected, and that the error count is minimal.
