Live data from Hacker News

Dropplets - A simple database-less CMS

dropplets.com

21–30 of 103 posts

Re: Dropplets - A simple database-less CMS

#22
This looks promising. I'm gonna give this a try since I'm looking for a simple and lightweight CMS for my blog. Speaking of which, anyone have any recommendations about that (apart from Jekyll)? I still haven't found what I'm looking for and I'm on the verge of coding my own blog in plain HTML instead of just installing something like Wordpress but that may be a pain in the ass to manage once I have more than handful of posts on my host.

But who knows, maybe Dropplets is the one.

Re: Dropplets - A simple database-less CMS

#23
Having tried it out before, I found the format used for blog posts to be incredibly arbitrary. It requires your twitter username for every post, and a bunch of other things. Plus, instead of using key/value pairings with yaml or something similar, it required that your headers be in a specific order.

It seems cool, it also seems like a little bit of work could be put into making it more accessible to people who didn't write it.

Re: Dropplets - A simple database-less CMS

#24
post #22

This looks promising. I'm gonna give this a try since I'm looking for a simple and lightweight CMS for my blog. Speaking of which, anyone have any recommendations about that (apart from Jekyll)? I still haven't found what I'm looking for and I'm on the verge of coding my own blog in plain HTML instead of just installing something like Wordpress but that may be a pain in the ass to manage once I have more than handful…

I started playing with Anchor last week. I like it thus far, because it really focuses on blogging, something WordPress kinda deemphasized two years ago.

Plus, it's pretty. Which is always a nice bonus.

----

If you're not averse to paying for something, Statamic looks really awesome.

Re: Dropplets - A simple database-less CMS

#25
post #9

Mods - I think this should be "CMS" (content management system) instead of "CRM" (customer relationship manager), as it's a blogging tool.

Maybe "blogging tool" would be the correct description, a cms is should support much more than just one content type.

Apparently the author would agree with you. The front page reads, "Dropplets is not a CMS, it's just for pure blogging and nothing more which is a good thing."

Re: Dropplets - A simple database-less CMS

#26
A small rant: I think it is bad practice to hide content below the page height. I just wanted to close the website because I thought 'nothing to see here' before I accidentally scrolled and more content was revealed.

Re: Dropplets - A simple database-less CMS

#27
post #18

Anyone looked at the code and see how this works? When you publish does it generate html or does it do it for each GET?

There isn't any caching. But, everything other than the index page can be generated fairly quickly, because you're not making database calls, only file system calls.

The index page could take a little longer.

Regardless, it's fairly quick, but it generates the output on each request. Which is to be expected, almost every other tool that isn't manually generated is the same.

Re: Dropplets - A simple database-less CMS

#28

Can someone please tell me how this is different from Jekyll? They both work based on the same concept if I'm correct? Also, how about support for category pages? I mean, show a page full of posts from one particular category only? Possible??

They work on completely different concepts:

Jekyll requires you to generate your site. Dropplets generates pages on each request.

Jekyll runs on your machine, and is written in Ruby. Dropplets runs on your server, and is written in PHP.

Jekyll's posts require very minimal metadata, and use a key/value pairing system with YAML. Dropplets' posts require a ton of metadata, and the same metadata for every post, and in a specific order, and you can't add arbitrary metadata.

----

I don't think Dropplets has categories, but I may be mistaken.

Post reply on HN