4 ms·
Blogger used to (maybe still does?) have an FTP option that would render a static version of your blog and push it to your own hosting account. Personally, tha
by callmeed 14y ago
Blogger used to (maybe still does?) have an FTP option that would render a static version of your blog and push it to your own hosting account.
Personally, that's what I'd like to see. A cms or email based blog that generates the static files and pushes them to whatever service/host you want (Dropbox, s3, github, FTP, SFTP, etc).
- arnorb 14y agoBlogger disabled that option a few years back. Some of us might even remember that before Blogspot came to, you had to have access to a server via FTP to publish.
- roberto 14y ago> Personally, that's what I'd like to see. A cms or email based blog that generates the static files and pushes them to whatever service/host you want (Dropbox, s3, github, FTP, SFTP, etc). This is what I've been doing, after Posterous announced its retirement: http://code.dealmeida.net/nefelibata http://code.dealmeida.net/nefelibata. You generate a static website from markdown files, publish it to configurable services (S3 initially, but it's plugin based), announce it to social networks (FB and Twitter). The idea is also that it will collect comments from FB and Twitter and add them to the static pages, so that discussion can happen on the social network du jour, but content will remain forever.
- coldtea 14y agoHow about some caching/proxy layer on top of Wordpress that both creates AND serves the static versions of the pages?
- callmeed 14y agoI mean, I think that's what some of the caching plugins do now , but in my experience they require a ton a configuration (e.g. a 100+ line .htaccess file). Plus I'm just not a fan of WP in general.