About The Author Lea is currently busy doing research in Human-Computer Interaction at MIT CSAIL. She has previously written an advanced CSS book for O’Reilly (CSS Secrets) and … More about Lea Verou …

Introducing Mavo: Create Web Apps Entirely By Writing HTML!

Smashing Newsletter Every week, we send out useful front-end & UX techniques. Subscribe and get the Smart Interface Design Checklists PDF delivered to your inbox. Your (smashing) email Subscribe →

Have you ever wanted to make a website that non-technical folks can edit right in the browser? Or have you ever wanted to make a website that presents an editable collection of items (e.g. your portfolio)? Or simply upload images to a website you made, right from the browser? Well, what if I told you, that you can do these things (and more!), just with HTML and CSS? No programming code to write, no servers to manage. You can make any element editable and saveable just by adding one HTML attribute to it. In fact, you can store your data locally in the browser, on Github, on Dropbox, or any other service just by changing an HTML attribute.

Make a website that non-technical folks (clients? family members?) can edit right in the browser

Make a website that presents an editable collection of items (your portfolio?)

Upload images to a website you made, right from the browser

Make an app to track and/or share an aspect of your life

Make a website that lets other people suggest edits to your data

Make an app that calculates something and presents the results in a custom way.

You can put your hand down now, it will get tired up there.

What if I told you, that you can do these things (and more!), just with HTML and CSS? No programming code to write, no servers to manage. You can make any element editable and saveable just by adding one HTML attribute to it. In fact, you can store your data locally in the browser, on Github, on Dropbox, or any other service just by changing an HTML attribute.

You can also turn any HTML element into a collection, with customizable controls for adding items, deleting items, and rearranging items via drag and drop. And your website visitors could suggest edits to your data that create Github pull requests behind the scenes, straight from your website.

What if I told you can dynamically display the results of calculations on this data anywhere in your UI with a syntax that is engineered to be easy to read and write, even by non-programmers? And that you can create dynamic, interactive websites with the same processes and hosting providers you use for static websites?

These are only some of the things you can do with Mavo, the project I’ve been working on for the past two years at MIT CSAIL and am excited to release today. Mavo is a language that extends HTML to describe applications that manage, store, and transform data. All you need to do to use Mavo in any HTML page is to include its two files. Yup, that’s it.

But how does it all work? Let’s look at a few examples.

Editable Homepage

Assume we have a run-of-the-mill static homepage, with the following HTML inside <body> :

<main> <h1> <img src="images/photo.jpg" alt=""> <span>Grumpy Cat</span> </h1> <p> <strong>Tardar Sauce</strong> (born April 4, 2012), commonly known as <strong>Grumpy Cat</strong>, is a cat, Internet and media personality and actress... </p> <div class="links"> <a class="twitter" href="https://twitter.com/RealGrumpyCat" target="_blank" title="Twitter">?</a> <a class="facebook" href="https://www.facebook.com/TheOfficialGrumpyCat" target="_blank" title="Facebook">f</a> <a class="wikipedia" href="https://en.wikipedia.org/wiki/Grumpy_Cat" target="_blank" title="Wikipedia">W</a> </div> </main>

_Photos and text taken from Grumpy Cat’s Wikipedia page._

Which, when styled looks like this:

By adding a few Mavo attributes, we can make it editable, and save its data to the cloud via Github (Github is only one of the supported services):

<main mv-app="homepage" mv-storage="https://github.com/mavoweb/data/homepage" mv-plugins="tinymce"> <h1> <img property="image" src="images/photo.jpg" alt=""> <span property="name">Grumpy Cat</span> </h1> <p property="description" class="tinymce"> <strong>Tardar Sauce</strong> (born April 4, 2012), commonly known as <strong>Grumpy Cat</strong>, is a cat, Internet and media personality and actress... </p> <div class="links"> <a property class="twitter" href="https://twitter.com/RealGrumpyCat" target="_blank" title="Twitter">?</a> <a property class="facebook" href="https://www.facebook.com/TheOfficialGrumpyCat" target="_blank" title="Facebook">f</a> <a property class="wikipedia" href="https://en.wikipedia.org/wiki/Grumpy_Cat" target="_blank" title="Wikipedia">W</a> </div> </main>

You can see the result in the video below or play with the live demo here.

But how did it work? What did we just do with all these attributes? Here is a breakdown:

[mv-app="homepage"](http://mavo.io/docs/primer/#mv-app) gives our app a name and tells Mavo to be active on this portion of the page.

gives our app a name and tells Mavo to be active on this portion of the page. [property](http://mavo.io/docs/primer/#property) attributes name important elements. By default, these elements will become editable and will be saved. The editing UI is generated based on the type of element, e.g. note that img is edited very differently from <a> or span . Of course, any generated UI is fully customizable.

attributes name important elements. By default, these elements will become editable and will be saved. The editing UI is generated based on the type of element, e.g. note that is edited very differently from or . Of course, any generated UI is fully customizable. The [mv-storage](http://mavo.io/docs/primer/#mv-storage) attribute tells Mavo where to store the data. Here its value is a (fuzzy) Github URL, so any data and uploads are stored on Github.

attribute tells Mavo where to store the data. Here its value is a (fuzzy) Github URL, so any data and uploads are stored on Github. mv-plugins="tinymce" loads the Mavo TinyMCE plugin for rich text editing, and class="tinymce" tells Mavo to edit this element via TinyMCE. Mavo is designed for extensibility, so developers that do know JavaScript can write Plugins that extend Mavo’s functionality or even completely change how it works. Using these plugins is as easy as adding an mv-plugins attribute to any element in your page.

Besides editability and persistence, one of Mavo’s cool features when used in conjunction with Github is that you can let visitors log in to send “edit suggestions” to your data, entirely via the same graphical interface you use for editing said data. These “edit suggestions” create pull requests behind the scenes that you can easily approve or reject.

To-Do List

At this point, we have demonstrated how Mavo can help get rid of CMSes for very simple websites. However, it can do a lot more. Let’s look at a very different example, a to-do app!

As before, we start with a static HTML mockup:

<main> <header> <h1>My tasks</h1> <p><strong>0</strong> done out of <strong>1</strong> total</p> </header> <ul> <li> <label> <input type="checkbox" /> Do stuff </label> </li> </ul> </main>

Which looks like this after some styling:

Can we use Mavo to turn this into a fully functional to-do list? You probably suspect what the answer is by now: Indeed we can! These are the changes we would need to make to our markup:

<main mv-app="todo" mv-storage="local" mv-mode="edit"> <header> <h1>My tasks</h1> <p><strong>[count(done)]</strong> done out of <strong>[count(task)]</strong> total</p> </header> <ul> <li property="task" mv-multiple> <label> <input property="done" type="checkbox" /> <span property="taskTitle">Do stuff</span> </label> </li> </ul> </main>

You can see the result in the video below or play with the live demo here.

So, what did we do here?

mv-storage="local" tells Mavo to store the data locally in the browser.

tells Mavo to store the data locally in the browser. You already know about property from the previous example. Note that it can also be used to group other properties.

from the previous example. Note that it can also be used to group other properties. [mv-multiple](http://mavo.io/docs/primer/#mv-multiple) is the Mavo feature that seems to excite people the most. It converts the element it’s on to an editable collection of items, full with controls to add and delete items, reorder items via drag and drop, and even keyboard shortcuts for all these!

is the Mavo feature that seems to excite people the most. It converts the element it’s on to an editable collection of items, full with controls to add and delete items, reorder items via drag and drop, and even keyboard shortcuts for all these! mv-mode="edit" tells Mavo that everything should be editable immediately, and does not need a separate read mode.

tells Mavo that everything should be editable immediately, and does not need a separate read mode. [count(done)] and [count(task)] are expressions, similar to those you may have used in spreadsheets. Expressions are written in MavoScript, an expression language designed to be readable, forgiving, and easy to use even by non-programmers. Experienced developers can also use JavaScript in Mavo Expressions.

Mavo does not treat HTML as merely a shortcut to JavaScript, but as the primary language for creating web applications. We have done actual user studies to prove that Mavo can be successfully used even by people with no programming experience, the results of which are published at ACM UIST 2016, one of the top academic venues for Human-Computer Interaction research. Our vision is that JavaScript, server backends, and databases should become the “Assembly of the Web”, mainly needed for specialized or high performance tasks. For everything else, HTML and CSS should suffice.

Want to know more? Go over to mavo.io, look at the Demos and read the Docs to understand more about the language.

Is Mavo perfect yet? Far from it. As with every project of this magnitude, there is much more work to be done than what has already been done, in every front. But it’s at a state where it can be useful, and demonstrate our vision for the future of Web development. We hope that others share that vision too, and (why not?) want to help us get there.