51–60 of 73 posts
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.)
Earlier quoted context omitted.
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.
This seems similar-ish, but with a self-hosted option - which I prefer after my experience when 900dpi shuttered ;)
Seems useful!
> If you're interested in kicking the tires and are comfortable with dev environments, then install the app via these terminal commands. 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? It looks great but I'm a bit confused by the intention.
Same here. The fact that you can request for a closed beta access suggest that it's not something you could host yourself, but at the end of the page it shows how to test it yourself. Pretty confusing. Edit: It says on the medium post: "This is a great way to get familiar with the app, and prep your site(s) for deploying on the Vapid hosted service." So yeah looks like it's going to be a SaSS.
"Vapid can be deployed to any hosting service that supports Node.js."
Earlier quoted context omitted.
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...
If that's true, it seems like the kinda missing bridge/glue between generators like Jekyll/Hugo; allowing static content without needing to be a web dev.
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.)
I was thinking Vapid is like http://getlektor.com and is a static renderer with a built-in admin UI. But you maybe correct that node.js is serving the files.
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/
I'm a big fan of Processwire (open source), and I also love that you need to define fields explicitly. Doesn't turn into a circus of what's defined where, when it gets a little bit complicated? I never tried this model so I'm really asking.
The main use case I think is for people who build landing pages for other people.
A static site generator is good if you're building a landing page for yourself, but if you're building a website for the butcher shop down the road, they're not gonna want to edit individual markdown files. So you throw in some Perch (or Vapid) variables and it does the rest for you. Then you can just give the shop owner a login and they can edit the site as they see fit.
The appeal is to have the ease of a static site generator (you don't have to develop your HTML with any sort of "CMS" in mind) while actually having that CMS functionality.
I'm excited about multiple products in this space, because it means I can probably switch between them in a matter of minutes/hours, realistically.
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?
- You create a bunch of static HTML pages with a bunch of tags like: {{field_name type=7_to_choose_from ...opts}}
- Vapid runs a node server that scans all your HTML files and parses out the tags in each html file
- The node server runs a CMS webapp (the "dashboard") that generates field inputs for the parsed tags (text inputs, image selectors, wysiwyg editors, etc... whatever matches your tag type)
- Data you input is persisted in a SQLite DB
- The node server serves up your static HTML pages as if they were any standard template (mustache, etc)
- It runs a watch server, so any changes to your files are auto updated
Onboarding demo seems to run as a 'development' server. Quick perusal of the docs don't describe what the production mode is (probably no watch server?).
That's all as far as I can tell. Seems fine for lightweight pages, as promised.