MetaBake is a development productivity suite. It should allow you to deliver 10 times faster then legacy development stacks/methodologies. We have found that - with MetaBake - the work of 6 developers over 6 months can be done by 3 developers in 3 weeks. We expect you to achieve the same productivity gains.
MetaBake productivity is based on three modules:
- nBake, a static site generation tool that runs locally;
- B-M-SPA, curated technologies and techniques that help you build dynamic apps and mobile apps faster;
- Meta, a bespoke cloud-based build and admin app infrastructure that helps deliver functionality to your clients more quickly.
We benchmark against LAMP, RAILS, MEAN and such. For example, LAMP is the technology WordPress was built on. Every 10 years or so technology gets 10 times better, which forces everyone to upgrade. Assembly was 10 times better than machine language. C/.js is 10 times better than Assembly. We believe that we found the answer on how to have a more productive team.
So far, somehow, server-side rendered LAMP has dominated web deployments, with WordPress having some 30% of the World Wide Web. It is time to start displacing that.
You can reinvest the time saved by using MetaBake into a more interactive user experience (UX). Better UX is proven to lead into higher user engagement and better user retention.
This section is about Meta, your bespoke cloud-based admin and build infrastructure; used on your web app. You need to know nBake first, but once you learn it, instead of using nBake CLI, you use Meta. (if you are not comfortable with nBake, go learn that first. Here we just wrap API around it.) In nBake you mounted your web app in the cloud, and with Meta, you admin|build is also in the cloud; both the web app and build are! That is what makes it Meta.
For a developer, Meta is akin to a build server like Jenkins. For others, Meta is akin to a custom WordPress or Shopify admin console.
When using Meta in the cloud, you no longer have to mount to S3 buckets locally. You would use the Meta admin UI to 'edit' code. For examples your users could use the bespoke Meta admin UI. These features should allow you to achieve additional productivity gains for your development team.
Developers would use CodeAnywhere or a similar IDE; no need for local development environment. Instead you use CodeAnywhere and Meta admin/build as a group; all in the cloud.
Meta in the cloud needs to mount to your S3 bucket so it can admin/build it. You install Meta on a Linux VM in a cloud; such as hosted by Digital Ocean.
Meta is meant to be bespoke/customized.