Is the name actually "rapid" but as said by Barry Kripke?<p>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.<p>Don't say RTFM because I did, but I didn't find anything like "why use vapid?". Is this point in the gist supposed to be the clincher?<p>> You only need to know HTML (plus CSS and JS to the extent that your design calls for it).
I like the look of it!<p>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!)<p>0: <a href="https://grabaperch.com/" rel="nofollow">https://grabaperch.com/</a>
Little nit-pick, but the code in the top image example says<p><pre><code> {{intro type=html required=false}}
</code></pre>
But there's still a red star next to intro
<a href="https://getkirby.com/" rel="nofollow">https://getkirby.com/</a> is nice, but not open-source. <a href="https://getgrav.org/" rel="nofollow">https://getgrav.org/</a> seems similar. <a href="https://bolt.cm/" rel="nofollow">https://bolt.cm/</a> is perhaps not as sparse, but the best flat file CMS I've found (SQLite).
I’m impressed with the illustration: it does a very good job of conveying just what the product is. It is, admittedly, much simpler than most products, but it’s quite an achievement all the same. I imagine that it’s a slight simplification, but perhaps only very slight.<p>It looks to have a couple of errors, though: the intro field in it doesn’t look right: the default editor type is wysiwyg, so I presume there should be a toolbar there in practice; and it has required=false, so I presume the red star should be missing.
I read<p>>The HTML is the CMS Add simple template tags to a static webpage, and Vapid will automatically generate the dashboard for you. No config files, no other languages required<p>While puzzling over the links (curved purple lines with end-points no arrows) over the image above. Then I guessed, HTML tabs can be added, and webform will update to reflect to the new tabs added. Right?<p>This took a good couple of minutes of thinking what this does. I suggest adding a video or two on the landing page with a demo. A before/after. Perhaps I'm stupid on not getting this, but I guess a lot of people are far more stupid than me.
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.)
Their first blog post talking about vapid is at:<p><a href="https://medium.com/@hellovapid/hello-vapid-db3709ad5b82" rel="nofollow">https://medium.com/@hellovapid/hello-vapid-db3709ad5b82</a>
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.<p>Will give it a try next week!
I took this for a test drive this morning. In addition to producing a raft of errors trying to install globally, I ran into a number of issues where the documentation didn't exactly jive with observed reality. I threw up my hands and wandered off when pasting example code from the documentation into a template caused the server to crash. General impression: fun idea, not ready for prime time.
This is great. I've been wanting something like this for a while now.<p>I really like the website too. Minus the small bugs people have already mentioned, the actual design and information on the front page is perfect. A lot of projects shared on HN could learn from this page, tbh (I mean that in an encouraging way, not an attack, but so many project homepages don't explain the project very well).
> If you're interested in kicking the tires and are comfortable with dev environments, then install the app via these terminal commands.<p>So is this actually an open-source project, or is the open source just intended as a preview, and it's expected that production workloads would always be in the SaaS version?<p>It looks great but I'm a bit confused by the intention.
A few years ago I used a small startup called 900dpi to build a few client websites that needed to allow the clients to modify certain parts of the website on the fly.<p>This seems similar-ish, but with a self-hosted option - which I prefer after my experience when 900dpi shuttered ;)<p>Seems useful!
Neat, haven't played with it but the execution looks great!<p>Have been working on something similar for a specific niche of CMSs, do you handle primitive lists/lists of complex types? (E.g. to create nav bars that can be modified by the CMS)
This looks really great, thank you!<p>I might play with it this morning, with Choo!<p><a href="https://github.com/choojs/choo" rel="nofollow">https://github.com/choojs/choo</a>