3 ms·
So, your setup is composed of as follows: Middleman: The template files. Siteleaf: The CMS for the end users to play with Prismic: The database. Heroku: The
by timepiece 12y ago
So, your setup is composed of as follows:
Middleman: The template files.
Siteleaf: The CMS for the end users to play with
Prismic: The database.
Heroku: The deployment esp. the scheduler part.
Amazon S3: The hosting.
Did I get it right?
- kaishiro 12y agoClose. Siteleaf/Prismic is an either or deal. Siteleaf is much simpler architecturally, and works for like 80% of my clients. You basically get page collections and optional meta data. Prismic is much more blown out - I bring it in as the big guns if I need to support a more complex hierarchy or need specific document masks/permission levels/etc. The deploy via Heroku is neat because it does a git clone of the repo on github before running the Middleman build (therefore consuming the API), so all I have to do is push my changes up to Github and they'll get picked up on the next pass (sometime in the next 10 minutes). It's just real fun to work with, with very few failure points. After all, the worst thing that happens is the build fails and they get served a 10 minute old static site.
- timepiece 12y agoNeat. Very neat indeed! How about your clients? Did they miss the old WP text editor or are happy with the new CMS? My only take on this setup is the perceived or apparent fragmentation since the resources are scattered over many places and not on a single point like in a typical WP installation, what do you think?