Live data from Hacker News

Vapid: an intentionally simple CMS

vapid.com

31–40 of 73 posts

Re: Vapid: an intentionally simple CMS

#31
post #20

Is the name actually "rapid" but as said by Barry Kripke? But a more serious question is, how is this different from the hundreds of other CMS? I am not attacking, but just trying to understand what motivated this and why someone might choose this. As someone who would need a CMS in the near future I am interested in this genuinely. Don't say RTFM because I did, but I didn't find anything like "why use vapid?". Is th…

It seems to be meant for people who build a lot of customizable, relatively simple websites. The devs write the HTML & CSS, and Vapid automatically generates admin dashboards for content management.

How is that different from what Django does?

Re: Vapid: an intentionally simple CMS

#32

Earlier quoted context omitted.

It seems to be meant for people who build a lot of customizable, relatively simple websites. The devs write the HTML & CSS, and Vapid automatically generates admin dashboards for content management.

How is that different from what Django does?

I think Vapid is for static sites. Unlike Django, WordPress, etc, there's no backend. Correct me if I'm wrong.

Re: Vapid: an intentionally simple CMS

#33
post #8

I like the look of it! The basic idea has been executed already using PHP by Perch CMS[0], but this looks like it could be a good alternative (esp. if it's open source!) 0: https://grabaperch.com/

Was going to come here to say https://grabaperch.com is similar and fantastic - Drew Mclellan and Rachel Andrew are so incredibly helpful in the forums and it's so easy to deploy it's my go-to for knocking out a site quickly for a friend.

Re: Vapid: an intentionally simple CMS

#34
post #20

Is the name actually "rapid" but as said by Barry Kripke? But a more serious question is, how is this different from the hundreds of other CMS? I am not attacking, but just trying to understand what motivated this and why someone might choose this. As someone who would need a CMS in the near future I am interested in this genuinely. Don't say RTFM because I did, but I didn't find anything like "why use vapid?". Is th…

Its selling point seems to be that it's "simple". Although for me Wordpress for instance is simple too in that it can be up and running within 10 minutes.

Re: Vapid: an intentionally simple CMS

#36
post #29
post #27

Nice, was actually checking out Jekyll the other day but this looks 10x better for the purpose of getting a simple blog up and running without all the WP bloat. Will give it a try next week!

I've quickly played with it just now and I can't see how you could use Vapid to create new blog posts. It seems to be a simple dashboard for existing content, but I couldn't figure out how to create new content.

If it supported markdown content as a type I could almost use it.

Re: Vapid: an intentionally simple CMS

#39
So, it is not a dashboard for managing a static site...rather, it is a dashboard for managing static content that gets ultimately served to visitors via node...is that right? (This is not a criticism, just confirming.)

Re: Vapid: an intentionally simple CMS

#40
post #20

Is the name actually "rapid" but as said by Barry Kripke? But a more serious question is, how is this different from the hundreds of other CMS? I am not attacking, but just trying to understand what motivated this and why someone might choose this. As someone who would need a CMS in the near future I am interested in this genuinely. Don't say RTFM because I did, but I didn't find anything like "why use vapid?". Is th…

Its selling point seems to be that it's "simple". Although for me Wordpress for instance is simple too in that it can be up and running within 10 minutes.

This is where we start spilling hate about Wordpress, but we won't, because we are better than that. Hold hands, everybody...
Post reply on HN