5 ms·
One thing that's really missing from the OSS world is a CMS that builds static content. We've got Jekyll, Hugo, Middleman and others that are really only target
by djsumdog 11y ago
One thing that's really missing from the OSS world is a CMS that builds static content. We've got Jekyll, Hugo, Middleman and others that are really only targeted at developers.
I'll admit, it's not easy. This is why CQ, Teamsite, et. al. cost a lot of money (insane amounts of money, oh and they're both terrible. CQ is good for end users, terrible for devs. Teamsite is just terrible, and cost $11k per website).
- antimatter 11y agoPerhaps this might be what you're looking for? https://www.getlektor.com https://www.getlektor.com
- therealmarv 11y ago+1 for lektor. But a cool bootstrap theme on top and you get anything you need like good categorization and pagination etc.
- deleted 11y ago[deleted]
- jgillich 11y agoProse[1] makes editing static sites quite easy. Unfortunately, the last time I tried it, it had lots of bugs and missing features, but seeing that there's been quite a lot of activity recently that might have changed. [1]: http://prose.io/# http://prose.io/#
- asteadman 11y agoThis is either much better than it was last time I saw it, or i've missed it entirely. Thank you!
- mapgrep 11y agoNo, this is a terrible idea that is being spread like a cancer by people who don't know their history. First of all, static rendering CMS-es are IN NO WAY missing as you say; in fact, as your own comment hints, such systems are incredibly abundant. There are MANY other static-render-HTML products that could be added to that list, and they stretch back into the 1990s. The basic problem with this approach is well understood: As the corpus of content on a given site grows, render time quickly approaches time between updates. In other words, you start waiting for renders to complete before you can change something else on the site. This happens in part because changes to a single particular piece of content often cause changes to multiple pages — think blog views, archive pages, index pages, tag pages, RSS feeds. Meanwhile, as a site grows, the number of contributors tends to grow, including authors, editors, illustrators, photographers. So not only are the static renders taking longer as the site grows, there is also a growing likelihood that someone will want to touch a piece of content in a given time period, thus triggering a new render. Probably the most high-profile example of how this could fail was when there were a lot of people using Movable Type for their blogs in the early 2000s; MT did static renders and many bigger blogs had switch to other blog engines or carefully operate around massive render times for MT sites. If you have a small personal site, static renders are fine. But SO IS BASICALLY EVERYTHING ELSE. You can build a personal site using any number of primitive-but-effective technologies, like server side includes, emacs macros — hell you could literally make a Microsoft Word template and publish everything from there via SFTP. On the flipside, you could install the most inefficient, computationally intensive, database driven crapfest of a web app and it won't matter because you don't need to scale. In other words, static CMSes are fine if you don't actually really need a CMS. By all means, for yourself, or a tiny project, use whatever you want. But we don't need MORE of those tools.
- asteadman 11y agoI don't think anyone is claiming that a static CMS would be a "good idea" for people who have a multitude of pages that are constantly changing, that is of course, madness. There are a huge number of websites (ie: like every small business website I have ever been to) that have like 5-10 pages tops and they almost never change. For all intents and purposes, they are static. Throwing such sites up on github or s3 is a no brainer. I disagree with your statement that we don't need MORE of those tools. We absolutely need more of those tools, but not for developers (there are literally a million to choose from if you are a developer), what we need are nice clean user-friendly front ends. Every time I have to enable javascript just to visit some Wix website I cringe a little.
- onion2k 11y agoThere are plugins for Wordpress that will bake the front end of the site in to static HTML and push it up to an S3 bucket for hosting. Seems like a decent solution to me.
- asteadman 11y agoUgh, Don't get me started on WordPress. I think I would describe such a solution as "lipstick on a pig".
- nilliams 11y agoOn HN you are generally expected to 'get started', rather than insulting projects like that without expanding. I would actually say, though I vastly prefer say Jekyll over WordPress, that generating a static site from a WordPress site probably works pretty well and gets you a very mature CMS UI for your users. Doing it that way round is probably preferable and better understood at this point than the newer solutions that are trying to bolt CMS backends onto Jekyll sites (CodeCannon, Prose.io etc).
- asteadman 11y ago
- owenwil 11y agoThat actually exists. A bunch of friends at Cloud Cannon built a front-end layer for Jekyll and it works really well: http://cloudcannon.com http://cloudcannon.com
- Tehnix 11y agoI think you just gave me my new side/hobby project :) A sort of CMS-like frontend to Hakyll (the Haskell Jekyll). I've tried to more or less sketch out the idea here https://github.com/Tehnix/hakyll-frontend https://github.com/Tehnix/hakyll-frontend.
- tootie 11y agoTeamsite costs way more than $11K. $100K at least. If you but their whole platform, it'll be closer to $500K
- hmartiniano 11y agoLektor (https://www.getlektor.com/ https://www.getlektor.com/) might be a good candidate for that. It has a graphical user interface which makes editing accessible for non technical folks.
- chrisparsons 11y agoBricolage in the late noughties was this. Salon ran it for a fair amount of time. The company I work for currently uses it, although I think we're one of the last ones, and since it's not really getting any updates anymore, we'll likely be moving off of it in the near future. It made some really novel decisions on the Admin UI spectrum, and it's not terrible for content managers as a lot of open source CMS software tends to be, but it never gained traction. My familiarity with Perl isn't what it should be, so it's always painful to try to dig in to debug problems as well.