A UI library that fully embraces web standards.

Some say it's the HTML6 we never got.

So modern it feels old!

Because UI should be fun 🥳

Does 👏 not 👏 suh 👏 port 👏 IE

It's freedom, baby. Yeah!

Standards #FTW

Code depressed? Call 1-800-M-DASH

24 components, 160 utility classes, and it's how small???

"Nothing is faster than nothing."
-Me

The AWS bill was $90 last month!!

You should stop reading this.

How many messages are there?

16, including this one.

Does it loop though?

No.

Mdash intends to leverage HTML, not replace it or try to outsmart it.
This makes Mdash ideal for all web projects and skill levels.
linkable tiny 6kb   responsive WCAG 2.1 very compatible zero dependencies

Quick start

This is the web. Let's use it.

or npm

What is Mdash

Mdash is a new kind of UI library. It's 100% standards-based and it's tiny.

Mdash components are comprised of standard HTML, custom HTML, and Custom Elements. As such, Mdash works with any framework (or no framework) and works with all types of web projects: SSR, SPA, PWA, static site, and even popular email clients.

What makes Mdash special

Quite literally, nothing. Nothing is exactly what makes Mdash special. There's no new concepts or abstractions. Nothing proprietary, no dependencies, not even a build step. As a result, no other UI library is as small or easy or familiar as Mdash.

Take a look around and compare Mdash's size and markup to see how "nothing" really is better.

Where did Mdash come from

Mdash is the result of building design systems in large engineering organizations where - for better or worse - tech stacks and architectures vary wildly, but the products still need to share common UI elements. It was during this time the TAC methodology was created with Mdash being the first open-source implementation.

 <m->

Compatible with everything

Mdash can be used anywhere HTML is used because it is HTML. Larger organizations especially benefit here because unlike other UI libraries, Mdash will work with all your products regardless of technology. To demonstrate, here's code samples of 13 different technologies all using the same Mdash component:

*Framework compatibility with Custom Elements is being tracked on custom-elements-everywhere.com. Today, all but one works with this standard.

Performance

Mdash is fast! Its execution speed comes from leveraging standards as much as possible in order to minimize code, retain browser optimizations, and eliminate dependencies. The latest JavaScript frameworks and virtual DOMs are still relatively expensive abstractions with execution overhead, and when it comes to code, nothing is faster than nothing!

In addition to execution speed, pages load faster because Mdash is so much smaller:

Mdash 6.8kb
Bootstrap 71.4kb
Material Web 79.5kb
Zurb Foundation 87.8kb
React Bootstrap 103.1kb
Material-UI 134.2kb
Semantic UI 174.3kb
Microsoft Fabric 244.1kb
Note: Sizes are min+gzip and include stylesheets, scripts, and runtime dependencies. In other words, this is the overhead before you've written your first line of code.

Installation

CDN

Just copy/paste these into <head>.

<link href="https://unpkg.com/m-@1.6.0/dist/min.css" rel="stylesheet">
<script src="https://unpkg.com/m-@1.6.0/dist/min.js" defer></script>

npm

npm install m-

Built assets including custom properties are located in dist/.

Browser support

Mdash works with the latest versions of:

Other modern browsers that support Custom Elements are likely to work, but are not tested (file a bug if you see something). IE is not supported and is unlikely to work even if you polyfill.

More about Mdash

The purpose

To make the UI layer incredibly simple and easy.

Mdash gives you a complete set of modern compatible-with-everything UI components instantly available from a CDN. No downloads. No CLI. No configuration. No build steps. No prespiling the virtual tree-shake lint matrix, or whatever. It does this by embracing HTML (and CSS and JavaScript) and relentlessly leveraging it. The result is a fun and uniquely small design system with standards-level longevity.

Depending on the kind of project you're working on, you can use Mdash on its own or alongside your framework of choice. In the latter case, the framework is responsible for the structure and state of your application while HTML and Mdash supply the final layer of UI.

Frameworks are misused

The UI layer of web applications has been overcomplicated and made dependent upon non-standard frameworks and methodologies that, in the context of generic UI components, do not add value. Frameworks are best applied to application-centric problems like routing, state management, and high-level product-centric component structure. Frameworks are not ideal for pure UI-centric problems like layout, shared UI elements, and generic styles.

The m- prefix

A prefix is required for any custom HTML (tags or elements). The "m" is for markup, because Mdash is all about that beautiful declarative markup! And no the name "Mdash" doesn't have anything to do with Lodash. It was suggested the proper name be changed from "M-" to "Mdash" to help with search engine results.

Design philosophy

Mdash believes in and is committed to the web platform. Developing on the web is awesome because:

Mdash was designed with all that in mind. It's why CDN install is the first option and not buried or unavailable as if linking to other resources on the internet is a last resort. It's why Mdash components are built with standard, approachable tech and not a popular JavaScript library. It's why there is no special syntax or proprietary ideas and why there's no dependencies. It's why the project is open source.

The intent of the Mdash API design is to be familiar. Where possible, Mdash matches native HTML, e.g. type="", name="", disabled, and when there isn't a native example to follow Mdash strives to use familiar patterns, e.g. dismissible="false" for Alert was chosen because it feels similar to the native draggable="false" attribute. If you could cover up all the m- prefixes in your markup, the hope is you couldn't tell the difference between native HTML elements and Mdash.

It's for everyone!

The web is an open platform accessible to everyone and so a design system for the web shouldn't require advanced knowledge just to get started, and it shouldn't require a commitment to learn a specific framework's idioms and API in order to make full use of it. Mdash serves true beginners equally as well as it does professional software engineers. So, whether you're building your first website or a large scale application with millions of users, Mdash helps you quickly build UI with significantly less code and with the longevity that only comes with standards-based code.