DEV Community

Ben Patton
Ben Patton

Posted on • Originally published at Medium on

Learnings from Planning a SvelteKit Course

Photo by Arnold Francisca on Unsplash

I am building a SvelteKit Course and I want to document what I am building here. It will be simple. It is a simple Markdown blog using MDsvex, tailwind, and Daisy UI.

Goals for this course are to give a brief overview of how to get started with SvelteKit and some of SvelteKit’s features. I have had to recon with the fact that there will always, always , be more to teach. So this course will be simple. Much simpler then I would like for it to be. But it will be a great starting point for those who are at my level, right below me, or want a really simple start to Svelte and SvelteKit.

But I want to start by addressing the pain that SvelteKit is solving.

Pain in Web Development

Now to start, I think it is important to say how awesome web development is. It is one of if not the easiest professions to change careers into because all the knowledge to learn the skills are available for free. It is work but within 6–12months anyone can learn the skills and get a job making decent money in the United States.

Often times the learning starts off with a lot of enthusiasm. I remember when I was learning html, css, and javascript at my bootcamp. I was in love with what I was doing. While we were learning these things we were also looking forward to the day that we learned React.

Again, clarity is needed. I love React. I will write another blog post soon on Remix is a web framework that sits on top of react and makes react development unfathomably easier. But again, more on that at another time.

When learning to code, html, css, and javascript are relatively simple to learn to be able to build a website. The excitement is real because you are actually putting something into the world. At some point you will levelup from html, css, and javascript to a framework.

Side note: I think we should do a better job of explaining, ‘why frameworks’.

But one thing that also happens, is as soon as you start to use a framework, there are a ton of other things you have to figure out and learn, about the framework. The typically feeling for me with this was that I always felt like I was adding a step of complexity.

Svelte: Removing Complexity

If I had been around the web development space long enough, I think React would have been a bigger deal to me. I know for those who have come before me and using all the various frameworks, React made some things really easy. But for new beginners, React becomes pretty complex.

Enter Svelte.

To quote a mentor:

Svelte is like glorified html

What does that mean? Instead of having 3 separate places you are working in code (the html file, the css file, and the javascript file), you have one component that houses your html, css, and javascript.

What is a component? Think of it like a lego. You can make individual components that do one thing, like a single lego block. But you can then compose components together to make larger components like a navbar, a layout, etc.

The bar to entry level for Svelte is very low. I believe Svelte is the best step for a developer after learning html, css, and javascript. Added to this is that Svelte now has SvelteKit, a framework on top of the Svelte to handle things like routing and a host of other necessities.

Top comments (0)