wayback-machine-downloader VS Hexo

I just found this https://github.com/hartator/wayback-machine-downloader

anyone have anything similarly interesting/cool/niche-useful ?

Send ArchiveTeam the link on IRC or here and we can save it to archive.org, then later you can use wayback-machine-downloader to grab it from archive.org.

https://github.com/hartator/wayback-machine-downloader

This is where it gets tricky, you need to download the code from the wayback machine and he was able to do that by following these steps: https://github.com/hartator/wayback-machine-downloader

Not sure if it will work for twitter, but I have used wayback-machine-downloader to batch download stuff.

Adding to archive.org, there is a github repo to fetch website data. You can give a try too. Here is the repo link

Edit: Good news! I found a solution that saved me. I was able to download the full website (including images, JS, and CSS files) using this tool: https://github.com/hartator/wayback-machine-downloader

Edit: Thank you to everyone who suggested the Wayback Machine Downloader! It saved the day and allowed me to download the full website, including images, JS, and CSS files.

I've used https://github.com/hartator/wayback-machine-downloader but it sometimes messes up CSS badly

A lot of great suggestions here and some stuff I’ve never heard of before!

Throwing my own suggestion into the ring, as I was just looking into this last week.

I started setting up a blog using Hexo. It’s another Node based SSG that uses markdown and supports tags. It has a lot of neat plugins that people have developed, too.

I like it so far!

https://github.com/hexojs/hexo

In my case, the latter is not possible because this blog is a static site, generated via Hexo and hosted on GitHub. It simply lacks a modifiable active server component.

Hexo — best lightweight SSG

Previously I've used Nuxt2 and even sooner - hexo.io

To make their creation easier, numerous open-source static websites generators are available: Jekyll, Hugo, Gatsby, Hexo, etc. Most of the time, the content is managed through static (ideally Markdown) files or a Content API. Then, the generator requests the content, injects it in templates defined by the developer and generates a bunch of HTML files.

https://gohugo.io/ written in go, support md https://hexo.io/ written in node

Hexo's

I'm currently using Hexo, I write articles in markdown, commit them to a git repository and push them to Github. I then have a Github Action to bundle the static website and publish it on Github Pages, so I get free hosting 👌

There are also many alternatives for selecting Static-Side Generating blog framework such as Hexo, Gatsby, Next.js (more details here). We will pick Hexo as our framework because it is a fast, simple & powerful blog framework.

Some alternatives I'm considering learning instead of Gatsby are Jeckyll or Hexo.