Static Website Generators • Hacker News Board

forlorn wrote: post #93

The main problem for me is that the absolute majority of them target blogs and if you try to adapt them for a more complicated website you gonna dive very deep inside the code or continue constant search. Now I look at hugo as it seems to be a more general-purpose tool that allows to play with structure and content types.

You should try Lektor (https://www.getlektor.com/). It has a flexible data structure with little assumption about the final product.

Re: Static Website Generators

#105

Post by stephengillie » Mon, Sep 19, 2016, 8:37 AM UTC

I made a somewhat unconventional static site generator in Powershell, as part of my Arkdata project. It produces flat HTML reports every minute, which IIS (or any other web server software) can simply serve. It calls a JavaScript file, as I was playing with sortable columns, but works without the file. I use a mobile CSS file for better mobile display too.

Github: https://github.com/Gilgamech/ARKScrape

Demo site (IIS up, but it's not currently generating reports): http://gilgamech.com/ark/PvP-Hardcore-OfficialServer92.html

Re: Static Website Generators

#106

Post by koevet » Mon, Sep 19, 2016, 8:39 AM UTC

What would be a sane deployment workflow for a static site generator, so that the static content ends up behind an Apache web server in my box?

edit markdown -> push github --> server does a pull -> builds -> deploy ?

Re: Static Website Generators

#107

Post by meritt » Mon, Sep 19, 2016, 8:52 AM UTC

Maybe I'm just oldschool but I've never understood the point of these. What's wrong with varnish + [any dynamic platform]?

Re: Static Website Generators

#108

Post by wazoox » Mon, Sep 19, 2016, 9:00 AM UTC

What about using whatever engine you want, then extract static pages with a script using good ol' wget -r ?

Re: Static Website Generators

#109

Post by masklinn » Mon, Sep 19, 2016, 9:06 AM UTC

Already__Taken wrote: post #99

bbx wrote: post #96

Earlier quoted context omitted.

I'm not sure if this counts as a "static website", since the page is not delivered exactly as stored . It requires JavaScript to actually renders the page, which seems like an overkill.

That's just client side templating. Which has the same problem they all do of being greeted with a white page until ALL the content is ready. If someone is prepared to accept this it's not that hard to accept generating the html page yourself and uploading that.

> That's just client side templating. Which has the same problem they all do of being greeted with a white page until ALL the content is ready.

Or being greeted with a white page period if you're using a non-JS enabled HTML client (noscript, CLI browser).

Re: Static Website Generators

#110

Post by rodgerd » Mon, Sep 19, 2016, 9:19 AM UTC

gregmac wrote: post #21

0xCMP wrote: post #12

I use Hugo for several websites and I enjoy it a lot. One favorite part is the ability to create content of different types.

This statement caught my attention in the article: > It is optimized for speed (Hugo sites can be built in milliseconds) Is that true, or does it just happen to be fast? It seems to me that the performance of a static site generation is irrelevant, and thus time spent on this is really wasted effort. I don't care if it takes several minutes to build.. it'll happen on the CI server in the background, and so long as th…

> It is optimized for speed (Hugo sites can be built in milliseconds)

I suspect it's based on a minimal set of test cases, not a full site. With hundreds of pages mine takes anything from 30 seconds to a couple of minutes to build.