4 ms·

This solution is sort of weird to me. To me, the allure of a static site or a static blog is to simplify the stack; To bring it back to the basics. Static HTML

by foxhop 10y ago

This solution is sort of weird to me. To me, the allure of a static site or a static blog is to simplify the stack; To bring it back to the basics. Static HTML served by a good ole-fashion web server. Adding the cognitive burden of "serverless" and/or lambda just to schedule seems to complicate something that isn't very complicated. Its almost like an invented problem. That said, long live this static site generator movement. I'm betting this movement will continue to grow which is why I'm bootstrapping https://www.remarkbox.com https://www.remarkbox.com (comments-as-a-service)

cocktailpeanuts 10y ago
I use jekyll NOT because it's simple (Actually it's 100 times more complex to use than a simple wordpress or medium) but because: 1. I can keep track changes with git 2. I can host them on Github pages for FREE 3. I own the content 4. More flexible In fact I've been really annoyed with all the boilerplate code and extensions I need to deal with in order to have a "usable" workflow set up, I almost thought about moving back to free blog services like medium, tumblr, wordpress, etc. but the only reasons I can't are the ones I mentioned above.
- foxhop 10y ago
  Jekyll is way more simple from a "stack" perspective. It has no database, has less moving parts. Wordpress is simple from an end user perspective. Services like medium and tumblr hide the complexity from its users. Its a trade off.
  - cocktailpeanuts 10y ago
    What you said is all correct. But my point was it's not just about "simplifying the stack". You said "the allure of a static site or a static blog is to simplify the stack;", but the thing is, not everyone thinks that way.
- codecurve 10y ago
  Simple != easy. Wordpress and co are easy, but they're fundamentally much more complex than static sites. Jekyll is quite simple, but it can be hard to use in comparison.
davidwells 10y ago
Thanks for the comment foxhop! We try to keep things as simple as possible where we can. This project came out of the need from our content team needing to publish content late at night and when people are out of office =) Check out the code https://github.com/serverless/post-scheduler/blob/master/handler.js https://github.com/serverless/post-scheduler/blob/master/han... this serverless service is just 2 functions that get deployed. It's a set it and forget it service =)
- foxhop 10y ago
  I think if I was doing operations for a company using a static site I would end up with something similar. I suppose my original perspective was coming from a one-person operation.
  - laktek 10y ago
    If you want the flexibility and performance of static sites, but don't want to deal with workflow setups, you should check Pragma - http://www.laktek.com/2016/11/29/introducing-pragma/ http://www.laktek.com/2016/11/29/introducing-pragma/
robryk 10y ago
A possible goal is to have the serving stack be as simple as possible. After all, you can argue that the publishing-side stack is anyway very complex: it includes e.g. the Github UI, if one makes edits using the Github UI.
geekjock 10y ago
Founder of https://buttercms.com https://buttercms.com here – we should talk!

by foxhop 10y ago

cocktailpeanuts 10y ago

I use jekyll NOT because it's simple (Actually it's 100 times more complex to use than a simple wordpress or medium) but because: 1. I can keep track changes with git 2. I can host them on Github pages for FREE 3. I own the content 4. More flexible In fact I've been really annoyed with all the boilerplate code and extensions I need to deal with in order to have a "usable" workflow set up, I almost thought about moving back to free blog services like medium, tumblr, wordpress, etc. but the only reasons I can't are the ones I mentioned above.

foxhop 10y ago
Jekyll is way more simple from a "stack" perspective. It has no database, has less moving parts. Wordpress is simple from an end user perspective. Services like medium and tumblr hide the complexity from its users. Its a trade off.
- cocktailpeanuts 10y ago
  What you said is all correct. But my point was it's not just about "simplifying the stack". You said "the allure of a static site or a static blog is to simplify the stack;", but the thing is, not everyone thinks that way.
codecurve 10y ago
Simple != easy. Wordpress and co are easy, but they're fundamentally much more complex than static sites. Jekyll is quite simple, but it can be hard to use in comparison.

davidwells 10y ago

Thanks for the comment foxhop! We try to keep things as simple as possible where we can. This project came out of the need from our content team needing to publish content late at night and when people are out of office =) Check out the code https://github.com/serverless/post-scheduler/blob/master/handler.js https://github.com/serverless/post-scheduler/blob/master/han... this serverless service is just 2 functions that get deployed. It's a set it and forget it service =)

foxhop 10y ago
I think if I was doing operations for a company using a static site I would end up with something similar. I suppose my original perspective was coming from a one-person operation.
- laktek 10y ago
  If you want the flexibility and performance of static sites, but don't want to deal with workflow setups, you should check Pragma - http://www.laktek.com/2016/11/29/introducing-pragma/ http://www.laktek.com/2016/11/29/introducing-pragma/

robryk 10y ago

A possible goal is to have the serving stack be as simple as possible. After all, you can argue that the publishing-side stack is anyway very complex: it includes e.g. the Github UI, if one makes edits using the Github UI.

geekjock 10y ago

Founder of https://buttercms.com https://buttercms.com here – we should talk!