Showing my inexperience

In one of my first blog posts on this site, I talked about things they don’t teach you in school and promised to write more as I continued my journey. In the post “My Experience with Frameworks,” I discussed the appeal of hosting anywhere as a reason I looked at front-end frameworks. Wow, did that show my inexperience with frameworks.

While researching SvelteKit, I read about how it could be hosted virtually anywhere. And that’s true—you can host a website made with SvelteKit anywhere, even on shared hosting. However, if you're going to use shared hosting, you must use the “adapter-static” tool in SvelteKit to turn your website into a static site.

What I didn’t know is that many frameworks have static site generators available, just like SvelteKit. To be clear, static site generators were not mentioned in any class I took at ACC. So, put SSGs in the category of things they don’t teach in school. I’ve learned that even Flask, the first framework I learned on my own, has a static page generator extension. A few options are Frozen-Flask for Flask, Django-distill in Django, the “next export” command in Next.js and using @nuxt/static in Nuxt.js. Researching any of those terms will give you all the information you need to proceed with the framework’s static generator. Additionally, Jekyll can be used alongside Rails and there are a number of SSGs that are based on a framework, such as Gridsome with Vue.js, Gatsby with React, Middleman with Ruby on Rails and Jigsaw with Laravel.

Again, these are just a few of the options that are available. I will definitely research these options in the future before making any assumptions.

Does this mean I’m going to start making all my sites static and hosting them on shared hosting? No, definitely not, but knowing the option is there is nice. To be honest, I think it’s time I “grew up” a little and stopped considering shared hosting as an option, but I think that discussion will be saved for another post.

Posted on: 2024-08-02 22:59:04.325174