Why Bedframe?

Browser extensions are just html, css and js

You've likely read that somewhere, right? And HTML, CSS and JS are your bread and butter so you think, "Ok! How hard can this be then, anyway?"

The Hero's journey

Then, the adventurous soul that you are, you wander the raw and naked internet searching... you become intimately familiar with the Github sort and filter functionality... the desert of the stale StackOverflow questions becomes thy constant friend... some things will work, some things will not... when was that template last updated? Is this answer still relevant?

To yourself you'll mutter, "This is a teenie tiny website I'm trying to build here! A lil app for the browser! Why is it so difficult?!"

What can be, unburdened...

You'll think about how good you have it in regular web dev world: you write code, raise a PR, merge to main and the Github actions lints, tests, builds and CDs your code to prod! Automatically. Continuously... "Can I have the same in extension land?, you'll wonder. No way i'm gonna have to set all that up myself! Convention over configuration... code as architecture and all that, right?!

Bedfellows

And that's how we become bedfellows, you and me! Bedframe gets you from prototype to — Github to web store — to profit a little faster than you otherwise would wandering the internet without a sherpa. You could do this all by yourself, there's nothing proprietary about it. Just good ol' conventions that simplify your path.

Why does Bedframe exist?

Beframe exists because its what you'll eventually arrive at when you finally say:

This is ridiculous! I want to build browser extensions like a fully grown adult human person! Basically: