3 ms·

> Static Site Generators how can that be detected ? I'm curious.

type0 7y ago
Or look for a link to the website source on github, gitlab etc and go from there. But that's more or less manual work given how many custom made SSGs there could be.
elcomet 7y ago
I'd say identify common templates? Or "made with Jekyll" blocks If it's a custom templates I think it's impossible.
stevekemp 7y ago
Some of them output META-tags, or footers such as "powered by XXX".
Lammy 7y ago
“generator” meta tag? https://html.spec.whatwg.org/multipage/semantics.html#meta-generator https://html.spec.whatwg.org/multipage/semantics.html#meta-g...
- saagarjha 7y ago
  Jekyll only adds that if you use their “SEO” plugin: https://github.com/jekyll/jekyll-seo-tag/blob/0943563d0aac6013187c742f38b90fc576075fda/lib/template.html#L6 https://github.com/jekyll/jekyll-seo-tag/blob/0943563d0aac60.... (I don’t use that plugin, so I add it manually to mine.)
  - Etheryte 7y ago
    If I'm not mistaken, Jekyll also adds it in the RSS feed metadata, if you use that plugin, but that's already a bit far fetched.
- etimberg 7y ago
  I checked my own site which is built with Hugo and that's what it uses <meta name="generator" content="Hugo 0.56.3">
nickjj 7y ago
I added this to my RSS feed: <generator>Jekyll v{{ jekyll.version }}</generator> But it's optional.
naniwaduni 7y ago
Only 22% did have any static site generator detected. Beyond that, 33% had a CMS detected. That leaves nearly half of analyzed sites as unknowns! Speculation aside on what might be effective aside, the real answer wrt OP is basically "it wasn't".
jefftk 7y ago
I generate my blog with a static site generator I wrote, but I don't see how anyone would be able to tell by inspecting the output. A heuristic that might work would be to add a cachebuster query parameter to the page url (?cb=$RANDOM) and see how long it takes to respond. The idea is that the three most common setups are: * static site served with apache/nginx/etc, which will just ignore the query param * dynamic site, which will regenerate the page * dynamic site behind a cache where the cache doesn't know that the query parameter isn't needed, and so the cachebuster will cause the page to be regenerated

Or look for a link to the website source on github, gitlab etc and go from there. But that's more or less manual work given how many custom made SSGs there could be.

elcomet 7y ago

I'd say identify common templates? Or "made with Jekyll" blocks If it's a custom templates I think it's impossible.

stevekemp 7y ago

Some of them output META-tags, or footers such as "powered by XXX".

Lammy 7y ago

“generator” meta tag? https://html.spec.whatwg.org/multipage/semantics.html#meta-generator https://html.spec.whatwg.org/multipage/semantics.html#meta-g...

saagarjha 7y ago
Jekyll only adds that if you use their “SEO” plugin: https://github.com/jekyll/jekyll-seo-tag/blob/0943563d0aac6013187c742f38b90fc576075fda/lib/template.html#L6 https://github.com/jekyll/jekyll-seo-tag/blob/0943563d0aac60.... (I don’t use that plugin, so I add it manually to mine.)
- Etheryte 7y ago
  If I'm not mistaken, Jekyll also adds it in the RSS feed metadata, if you use that plugin, but that's already a bit far fetched.
etimberg 7y ago
I checked my own site which is built with Hugo and that's what it uses <meta name="generator" content="Hugo 0.56.3">

nickjj 7y ago

I added this to my RSS feed: <generator>Jekyll v{{ jekyll.version }}</generator> But it's optional.

naniwaduni 7y ago

Only 22% did have any static site generator detected. Beyond that, 33% had a CMS detected. That leaves nearly half of analyzed sites as unknowns! Speculation aside on what might be effective aside, the real answer wrt OP is basically "it wasn't".

jefftk 7y ago

I generate my blog with a static site generator I wrote, but I don't see how anyone would be able to tell by inspecting the output. A heuristic that might work would be to add a cachebuster query parameter to the page url (?cb=$RANDOM) and see how long it takes to respond. The idea is that the three most common setups are: * static site served with apache/nginx/etc, which will just ignore the query param * dynamic site, which will regenerate the page * dynamic site behind a cache where the cache doesn't know that the query parameter isn't needed, and so the cachebuster will cause the page to be regenerated