Low-code productivity for programmers via generators for Pug, Markdown and much more; including dynamic data binding.
Metabake is a development productivity suite. It should allow you to deliver 10 times faster than 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.
How does open source Metabake deliver 10X faster and cheaper web app development? Not enough organizations are fully leveraging the new Serverless. With Serverless services like Firestore and S3 you get rid of ALL server-side and middleware development and operations. This is where up to 2/3 of your time and cost used to go. Gone!
The Metabake approach has 10 pillars that are the foundation for achieving mind-blowing development productivity gains. I'll just mention one more pillar here: automatic programming. You've probably heard of 'static site generators' like Hugo or Jekyll that people use to generate their web site or a blog. Automatic programming means using a similar generator to write your web app! This can get you to yet another level of productivity.
To learn more about the Metabake approach, including all 10 pillars and full examples, go to metabake.net. Or, to dive in right away, use the 'mbake CLI' from github.com/metabake as the first step into 10X faster web app development.
Metabake productivity is based on three modules:
- mbake, 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 mbake first, but once you learn it, instead of using mbake CLI, you use Meta. (if you are not comfortable with mbake, go learn that first. Here we just wrap API around it.) In mbake 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.