I like systems that keep your work focused & simple.
Vapid: an intentionally simple CMS
71–73 of 73 posts
Re: Vapid: an intentionally simple CMS
#72Earlier quoted context omitted.
Because in my (somewhat limited) experience with CMSs' the definition of the data in separate from the layout, which makes sense if you're building a larger site where separation of view and data makes maintenance easier. However, if all you're doing is building a 5 page website, it's much simpler to just put in the configurable parts in the HTML as you're building it and let Vapid handle the dashboard, which the cli…
> However, if all you're doing is building a 5 page website, Why not cut to the chase and show the client how to use FTP and a text editor? Why add more complexity beyond that?
Re: Vapid: an intentionally simple CMS
#73I 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/
Honestly, I'm excited for Vapid. I've always loved implementing CMS systems. WordPress is great, with undoubtably the largest community of plugins and templates, and like the new Gutenberg editor... but I'm also starting to fall in love with the JAMstack model (i.e. Netlify, Headless CMS). Simply pushing commits to Github and sitting back. Netlify Forms is nice and easy, but their CMS sucks IMHO. Which is why I'm excited for something like Vapid. It fills that void I'm feeling.
I can picture myself spinning out all these nice custom CMS websites for clients and maybe building some custom browser plugins to make it so easy for clients (like how Tipe.io does). That feels like the future / next level.