Sent on May 17, 2022

The hard part about Static Site Generators

There is a steep learning curve for someone who’s going from basic HTML, CSS, and JavaScript, to building a website with a Static Site Generator.

There are two major blockage points:

  1. How do you use a Static Site Generator?
  2. What if you screw up SEO?

We’ll cover both of these points today.

How do you use a Static Site Generator?

All Static Site Generators share the same principles:

  1. You split HTML up into chunks
  2. You include these chunks into specific HTML files
  3. You run a command to compile the chunks into the HTML files.

But all Static Site Generators behave differently. You want to consider which one to use because adopting a new ecosystem takes energy and effort.

There are lots of decisions to be made. You have to consider:

  1. How do you write pages
  2. How do you include your assets (like images, CSS, JS, SVGs, etc)
  3. How do you create a good folder structure
  4. How do you create reusable components
  5. … The list goes on

There are lots of decisions to make when you build your first website with Static Site Generators. This is why there is a steep learning curve—you have to learn about the decisions you have to make.

The problem is documentations don’t tell you about the decisions you need to make.

The documentation for each Static Site Generator is built to teach people how to use their Static Site Generator. They don’t care about what you need to know to make a good website. In fact, most Static Site Generator documentation assume you know what you need to know.

(Then again, tell me which documentation doesn’t assume you know something… this is a big problem with web technology, not with you).

For someone who is new to Static Site Generators, you’re going to be overwhelmed and confused when you read the documentation. That’s normal. It’s okay. You’re not a stupid person.

You simply don’t have the experience.

This is where I come in.

I have been building websites with Static Site Generators for years. I spent hundreds of hours digging into documentation and building stuff. I know what to watch out for. I also know what to teach you to create a robust Static Site Generator**.**

  • There’s a way to write good code.
  • There’s a way to write code that’s so easy to use and understand — to a point where a non-coder becomes excited to use the system I created. She even paid me $2000 to port her Wordpress website to my system.

I’ll tell you more about my system tomorrow.

For now, let’s talk about the #1 challenge people face when building a static website—SEO.

What if you screw up SEO?

SEO stands for Search Engine Optimization.

People who are switching over from CMSes like Wordpress to Static Site Generators have a fear of screwing up SEO. And that’s understandable.

If you screw up SEO, your site doesn’t get listed on search engines like Google. Screwing up is bad because you want people to find your website!

The truth is: SEO is not as hard as you think. You just need to get a few things right:

  1. Title tags
  2. Description
  3. Heading tags
  4. Links
  5. Canonical links

I’ll show you how to do these things in my system.

If you need proof, 1 million people visited my website in 2021. It’s not that much compared to the big names, but it’s sufficient enough to prove that I know some SEO chops—that you may miss when you’re building your own Static website.

In short, don’t worry about SEO. I got you covered.

Should you learn to use a Static Site Generator?

Static Site Generators have a steep learning curve, but they are absolutely worthwhile for three reasons:

  1. They’re easier to learn compared to things like Wordpress
  2. You get full control (and flexibility) over your frontend code
  3. You can learn it once and use it forever

It’s a worthwhile investment because they let you build sites with a much better experience as a developer (and hint: they also let you build sites that provide a much better experience than what Wordpress can give).

Ultimately, I want to make it easy for you—especially as a beginner developer—to put up your website in the most developer-friendly way.

I hate using stuff that’s not friendly so I always make my workflows friendly. It is so friendly that I can set this system up for a non-coding client, and she’s happy to use it.

I’ll tell you the story tomorrow.

I got three questions for you for today:

  1. Why do you want to build a website?
  2. What’s the hardest thing you experienced about building a website?
  3. Are you interested in hearing about my system?

Reply and let me know. I read every message. I look forward to hearing from you.

Stay awesome,
Zell

P.S. There’s a learning curve for someone who’s going from basic HTML, CSS, and JavaScript to a Static Site Generator. But this learning curve is not as steep compared to learning a new backend language like PHP or Ruby.

If you’re considering learning Wordpress or something similar, consider learning a Static Site Generator instead!