[HN Gopher] Perch: a really little CMS
       ___________________________________________________________________
        
       Perch: a really little CMS
        
       Author : Tomte
       Score  : 30 points
       Date   : 2020-02-18 19:12 UTC (3 hours ago)
        
 (HTM) web link (grabaperch.com)
 (TXT) w3m dump (grabaperch.com)
        
       | blowski wrote:
       | The "elephant in the room" I couldn't find answered on the site:
       | if I'm going to use a PHP CMS, why would I not use WordPress or
       | Drupal? They both have an enormous community of developers,
       | plugins, documentation, and users. At the moment, this feels like
       | yet another PHP CMS that will become abandonware within months.
        
         | brundolf wrote:
         | WordPress is a nightmare as soon as you have to go beneath the
         | surface. The community around it definitely has value, but the
         | tradeoff is a bloated monolith that you have to become an
         | expert in if you want to do any customization beyond drop-in
         | plugins.
        
         | ChrisLTD wrote:
         | Perch has been around for a decade. You never know when or if
         | something will become abandonware, but Perch isn't something
         | new.
        
           | blowski wrote:
           | I didn't realise it had been around for so long. Thanks for
           | pointing that out.
        
           | tylerchilds wrote:
           | Just a shoutout to Rachel Andrew, the co-founder of Perch,
           | member of the CSSWG and imo the Champion of CSS Grid.
           | 
           | https://rachelandrew.co.uk/
        
         | oakesm9 wrote:
         | Perch was first launched in 2009 and is very different in
         | architecture from WordPress or Drupel.
         | 
         | https://grabaperch.com/news?page=33
        
         | [deleted]
        
         | jpswade wrote:
         | It's little. I think perch has been around for about 10 years
         | or more.
        
       | Nickersf wrote:
       | I love it. Use it for client work to this day.
        
       | vorpalhex wrote:
       | There's a ton of these little php CMSs but it feels like
       | inheritating the entire attack surface of LAMP or even just an
       | apache + php stack is insane these days.
       | 
       | Use a static site generator. Maybe have a nice UI around it.
       | Publish the whole thing to S3 or whatever CDN fronted storage
       | solution you like. Almost no attack surface, mindlessly easy,
       | very cheap.
        
         | brundolf wrote:
         | > Use a static site generator.
         | 
         | Regardless of how you serve the end-user site (generated ahead-
         | of-time or at request time), there's enormous value in backing
         | it with a database and providing non-technical maintainers a
         | friendly UI over that database for managing their own content.
         | If you want something more minimal than the OP, you might go
         | look up something called "Headless CMS".
        
           | ncphillips wrote:
           | Forestry.io is a headless CMS that is backed by Git. It is
           | made for Static Site generators and the content is still kept
           | in your repository.
        
           | fenwick67 wrote:
           | I'd love to see a CMS that runs on your local PC to drive a
           | well-known static generator (Hugo, jekyll etc). This seems
           | like the best of both worlds; no attack surface and easy to
           | use.
        
             | thrwaway69 wrote:
             | https://getpublii.com/
             | 
             | There are others as well.
        
           | smacktoward wrote:
           | There's nothing saying you couldn't provide a friendly UI _on
           | top of_ a static site generator. The first big hit CMS for
           | publishing blogs, Movable Type
           | (https://en.wikipedia.org/wiki/Movable_Type), worked exactly
           | that way -- it used MySQL as its content store and provided a
           | nice WYSIWYG interface for working with content, but when you
           | hit "Publish" it ground out your site as a set of static HTML
           | files.
        
             | brundolf wrote:
             | The parent comment seemed to be suggesting that people use
             | a static site generator "instead of a CMS". Part of what I
             | was trying to do with my comment is point out the
             | orthogonality of the two. A static site generator is just a
             | glorified cache over a normal web server.
        
         | kroltan wrote:
         | Kinda agree. I use Airtable as the CMS for my personal website,
         | and it's actually pretty quick to whip up pages with Gatsby (or
         | whatever floats your boat in terms of SSG), then throw it onto
         | some hosting and tada!
         | 
         | I even made some webhooks so I can trigger rebuilds from within
         | Airtable, so when I change stuff I don't need to worry about
         | going to the host and manually clicking rebuild.
        
         | Tomte wrote:
         | > Maybe have a nice UI around it.
         | 
         | I only know about Lektor and MovableType. Arte there more SSGs
         | with some kind of web interface to write and edit posts?
        
           | raben_ wrote:
           | publii has a very well polished GUI https://getpublii.com/
        
           | tekknolagi wrote:
           | Jekyll has jekyll-admin: https://github.com/jekyll/jekyll-
           | admin
        
           | marc_io wrote:
           | Use Stackbit to create your combo of SSG, Theme and CMS.
           | https://www.stackbit.com/
        
           | vorpalhex wrote:
           | Forestry.io supports an entire mess of site generators
           | including Hugo and Jekyll. You can also leverage Github or
           | Gitlab's ui directly to edit or create files.
        
           | Doches wrote:
           | Forestry.io is a nice wrapper around a bunch of SSGs, backed
           | by git. It's a paid subscription, but with a pretty generous
           | free tier. I'm using it so my less-technical co-founders can
           | edit our Jekyll-based support site.
        
         | squarefoot wrote:
         | I was just thinking that static site generators would deserve
         | their own awesome list, and there we go. Someone already made
         | one.
         | 
         | https://github.com/myles/awesome-static-generators
        
           | pvorb wrote:
           | https://staticsitegenerators.net/ includes a comprehensive
           | list and has been around for a while.
        
             | squarefoot wrote:
             | Even better, and sortable. Thanks!
        
         | tunesmith wrote:
         | You can also use something like NextJS's static pages, where
         | you can still use React for client-side interactivity that
         | doesn't require dynamic server communication.
        
       | jitl wrote:
       | I used Perch for freelance web development back in '10 and it was
       | great - just the features I needed, and simple enough to share
       | with clients. Well worth the price.
        
       | benfrain wrote:
       | "It's all about the comments". All these static site generators
       | are fine but they can't deal with comments. Then you have to add
       | a commenting system from a 3rd party, at which point you may well
       | wish you'd just gone with a PHP/DB solution from the beginning
        
         | winrid wrote:
         | Well I just launched fastcomments.com which you could use :p
        
         | markandrewj wrote:
         | You can use webhooks for this. As an example:
         | https://staticman.net/docs/
        
       | deminature wrote:
       | Seems great, but gating the demo behind an email signup seems
       | like it would bounce a lot of potential customers. It certainly
       | killed my interest in looking at the demo.
        
       ___________________________________________________________________
       (page generated 2020-02-18 23:00 UTC)