10 ms·

As many others indicated, static sites are much better unless you need dynamic features. Static sites make deployments much easier, doesn't depend on any OS/run

by alpb 9y ago

As many others indicated, static sites are much better unless you need dynamic features. Static sites make deployments much easier, doesn't depend on any OS/runtime, doesn't lock you in to a particular database. You just write markdown and with little to no modification, the same thing could just work on Hugo, or Jekyll.

scrollaway 9y ago
I use Jekyll; I used Hugo and Pelican in the past. They solve a very specific use case. But if you want to allow guest posting on your blog, a static site will not do. You need something that has drafts, that has a proper editor, that has a UI you can add and invite people to. Ghost solves that.
- TaylorAlexander 9y ago
  Ghost has drafts, and the editor is fine for me (plain text markdown with instant preview). I think(?) it also supports multiple logins with permission management? I feel like adding a user requires an admin (no self sign up that I know of) but other than that, I think it might do what you’re talking about. I use ghost for my personal site and I love it. (Not that I use multiple authors.)
  - scrollaway 9y ago
    I think you misread my reply. I'm bringing these things up because Ghost can do them.
- remir 9y ago
  Netlify CMS solved the problem you described. https://www.netlifycms.org/ https://www.netlifycms.org/
  - bmc7505 9y ago
    In theory, is there any reason why this couldn't support git-based comments as well? Maybe through a PR-style interface?
    - erquhart 9y ago
      There's a tool called staticman - it doesn't integrate with Netlify CMS (yet), but it's a great git-based comments solution: https://staticman.net/ https://staticman.net/
- x0x0 9y ago
  We use butter [1] for that, and we're liking the product so far. The various nontechnical people (ceo, writers) have been fine with it. Butter build and distribute a gem that just drops into rails and displays your posts. You have to style it, but you get the erb files. They do have some support for local caching, but investigating that is on my todo list. One big upside of this design is seo: your blog isn't on blog.domain.com, but wherever you want it on your main site. [1] https://buttercms.com/ https://buttercms.com/
- neya 9y ago
  Netlify + Jekyll can get this done with some amount of customization. Static, but using Netlify's identity service. This has worked well for me for many clients.
- shaqbert 9y ago
  You need a headless CMS like Contentful[0]. They have a free developer tier which is great for static sites, especially when you pair it with the super awesome React based static site generator GatsbyJS[1]. [0]: https://www.contentful.com/ https://www.contentful.com/ [1]: https://www.gatsbyjs.org/docs/gatsby-starters/ https://www.gatsbyjs.org/docs/gatsby-starters/
  - __bee 9y ago
    would go with Ghost or Hosted Jekyll, `Contentful` is not a good solution for individual/small/medium teams.
    - dgreensp 9y ago
      Why not?
    - gitgud 9y ago
      I'm not familiar with the service, why isn't a it good for individual/small/medium teams?
    - jdavis703 9y ago
      I was an early user of Contentful. Before I introduced it, we had non-techies editing YAML or Markdown files and committing them to Git and deploying them using Jenkins (yeah that went about as well as you'd expect). After countless hours supporting this system I decided to move over a couple of the content pages to Contentful (here's one example: https://issuu.com/m/success/madsounds https://issuu.com/m/success/madsounds). I didn't need to support anyone after making that move. As techies we tend to think things like Git are easy, but it's not (that's part of the reason we get paid the big bucks( Also eventually basically all the company's CMS needs were moved over to Contentful. From my experience it scaled well for both small and medium-sized teams.
  - nvus 9y ago
    I want to upvote you more.
- mseebach 9y ago
  It seems that all of those features are Git-features. The missing piece is a "git-aware" markdown editor, as in, an editor that knows about git branches, and can commit/push and be mildy helpful if there's a conflict.
RobGav 9y ago
Easy to use for non technical users is Publii https://getpublii.com https://getpublii.com It works like a dynamic CMS but generates static output, comes with GUI and clean, lightweight free themes.
- iagovar 9y ago
  Publii is fishy, they dont have public repos
  - RobGav 9y ago
    Fishy? :) Next month should be released the first stable version with rewriten backend (based on Vue) and GitHub repo.
    - type0 9y ago
      Are there any plans for Linux release?
jamalone 9y ago
As a fan of Ghost’s design and preferring static sites, I started using Jekyll with the theme Jasper2, which was based on Ghost’s default theme Casper. Super easy to set up and use if you’re comfortable with not having the ghost editor, and with github pages hosting and publishing was a breeze.

by alpb 9y ago

scrollaway 9y ago

I use Jekyll; I used Hugo and Pelican in the past. They solve a very specific use case. But if you want to allow guest posting on your blog, a static site will not do. You need something that has drafts, that has a proper editor, that has a UI you can add and invite people to. Ghost solves that.

TaylorAlexander 9y ago
Ghost has drafts, and the editor is fine for me (plain text markdown with instant preview). I think(?) it also supports multiple logins with permission management? I feel like adding a user requires an admin (no self sign up that I know of) but other than that, I think it might do what you’re talking about. I use ghost for my personal site and I love it. (Not that I use multiple authors.)
- scrollaway 9y ago
  I think you misread my reply. I'm bringing these things up because Ghost can do them.
remir 9y ago
Netlify CMS solved the problem you described. https://www.netlifycms.org/ https://www.netlifycms.org/
- bmc7505 9y ago
  In theory, is there any reason why this couldn't support git-based comments as well? Maybe through a PR-style interface?
  - erquhart 9y ago
    There's a tool called staticman - it doesn't integrate with Netlify CMS (yet), but it's a great git-based comments solution: https://staticman.net/ https://staticman.net/
x0x0 9y ago
We use butter [1] for that, and we're liking the product so far. The various nontechnical people (ceo, writers) have been fine with it. Butter build and distribute a gem that just drops into rails and displays your posts. You have to style it, but you get the erb files. They do have some support for local caching, but investigating that is on my todo list. One big upside of this design is seo: your blog isn't on blog.domain.com, but wherever you want it on your main site. [1] https://buttercms.com/ https://buttercms.com/
neya 9y ago
Netlify + Jekyll can get this done with some amount of customization. Static, but using Netlify's identity service. This has worked well for me for many clients.
shaqbert 9y ago
You need a headless CMS like Contentful[0]. They have a free developer tier which is great for static sites, especially when you pair it with the super awesome React based static site generator GatsbyJS[1]. [0]: https://www.contentful.com/ https://www.contentful.com/ [1]: https://www.gatsbyjs.org/docs/gatsby-starters/ https://www.gatsbyjs.org/docs/gatsby-starters/
- __bee 9y ago
  would go with Ghost or Hosted Jekyll, `Contentful` is not a good solution for individual/small/medium teams.
  - dgreensp 9y ago
    Why not?
  - gitgud 9y ago
    I'm not familiar with the service, why isn't a it good for individual/small/medium teams?
  - jdavis703 9y ago
    I was an early user of Contentful. Before I introduced it, we had non-techies editing YAML or Markdown files and committing them to Git and deploying them using Jenkins (yeah that went about as well as you'd expect). After countless hours supporting this system I decided to move over a couple of the content pages to Contentful (here's one example: https://issuu.com/m/success/madsounds https://issuu.com/m/success/madsounds). I didn't need to support anyone after making that move. As techies we tend to think things like Git are easy, but it's not (that's part of the reason we get paid the big bucks( Also eventually basically all the company's CMS needs were moved over to Contentful. From my experience it scaled well for both small and medium-sized teams.
- nvus 9y ago
  I want to upvote you more.
mseebach 9y ago
It seems that all of those features are Git-features. The missing piece is a "git-aware" markdown editor, as in, an editor that knows about git branches, and can commit/push and be mildy helpful if there's a conflict.

RobGav 9y ago

Easy to use for non technical users is Publii https://getpublii.com https://getpublii.com It works like a dynamic CMS but generates static output, comes with GUI and clean, lightweight free themes.

iagovar 9y ago
Publii is fishy, they dont have public repos
- RobGav 9y ago
  Fishy? :) Next month should be released the first stable version with rewriten backend (based on Vue) and GitHub repo.
  - type0 9y ago
    Are there any plans for Linux release?

jamalone 9y ago

As a fan of Ghost’s design and preferring static sites, I started using Jekyll with the theme Jasper2, which was based on Ghost’s default theme Casper. Super easy to set up and use if you’re comfortable with not having the ghost editor, and with github pages hosting and publishing was a breeze.