loading...

re: What is Going on With Static Site Generators? Why the numbers are increasing? VIEW POST

FULL DISCUSSION
 

I think it stems from us (as tech nerds) constantly wanting to optimize and automate so we have more time for other things. Want to spin up a site? Just use the generator and put in a little bit of content into the template and boom website. Want to blog? Barely any set-up -- just use a generator and put the posts in the template and done. It takes all the configuration and tinkering of setting up a new project and boilerplates it, so all the end-user has to do is write copy and not worry about the rest.

Or maybe I'm just lazy and only tinker when I'm in a tinker mood ;)

 

I agree JAMStack is impressive. but the problem is there, I think Users are divided into so many groups there - Hugo - Jekyll and 50+ static site generator (You can check out the comments of my other post). People tried many Static Site Generators but they got stuck in many Problems and when they try to debug it(Google). What did they find? Just Official Docs(Crap for now!) What?? The Stats say that 60000 users are using this static site generator. So where are the response? Why No Good-Tutorials are available? Why Google is so much blank? Then they move to second SSG and then third SSG and then boom!
I know it's easy to create a website but Custom Theming, Plugins and many more. I think we must pivot! Improve the docs of the best solution for everyone and populate the community with it by writing articles and making YouTube videos. We can't handle so many Static Site Generators

 

As a tech nerd, I love optimizing my work. As far as setting up a repo on GitHub, I'm perfectly happy - my work can be available to the public, and it doesn't cost me $100-$200/year for hosting; instead, it costs nothing. So far, so good. So, how do I present my repo to the world? Well, the 'code' page for the repo works, but it's not pretty. I can either pay for hosting anyway, or I am forced to use Jekyll.

You see, I've already designed and developed everything in the repo to make it presentable for users. So, I push it with Jekyll, and I get what I pay for. The website generation is technically free, from a purely financial standpoint, but the cost in time (about 2 weeks) is astronomical in terms of 'optimizing' the automatic process by adding multiple hurdles surmounted only by way of the CLI and which adds mountains of excess, tangled code to the whole project.

Correct me if I'm wrong, but I thought optimizing was supposed to be more about getting rid of cruft and bloat, not adding as much as possible. Now if only there was a way to just let people open the index page instead of seeing it as a file halfway down a list of files, but without the need for juggling in the CLI or the addition of additional code, like a pre-made custom theme that I had to choose and also create more code for in order to override and replace with the CSS files already included in the repo...

 
Code of Conduct Report abuse