material-web
spectrum-web-components
Our great sponsors
material-web | spectrum-web-components | |
---|---|---|
10 | 15 | |
8,604 | 1,177 | |
4.1% | 4.2% | |
9.8 | 9.8 | |
3 days ago | 1 day ago | |
TypeScript | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
material-web
- Web Components e a minha opinião sobre o futuro das libs front-end
-
Making Web Component properties behave closer to the platform
For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.
-
Google Material Web
Guess there was a 1.0 3 weeks ago: https://github.com/material-components/material-web/discussi...
-
I shaved 80 MB from my TypeScript build by removing googleapis
There is a new “official” one in the works here [1] that uses lots of the “latest and greatest stuff” and should be very fast when it’s finished (later this year). As far as I know it’s set to become the new default company wide implementation of Material on web.
[1] https://github.com/material-components/material-web
-
Using native form with web components + felte no data being passed
I'm using material-web web components inside a form with felte.dev
- Easiest Front-End framework for backend developers?
-
Phoenix with Material Design
If you're going for full SSR and don't want to have to worry about JavaScript, I'd just grab the MDC web components library from Google. That's going to be the easiest time you'll have without implementing a front end framework.
-
Announcing Silkenweb: A reactive VDOM-less web framework using plain rust syntax
Ultimately, I'd like to be able to write reasonably complex client/server web apps in Rust, so the next medium term thing on my list is web components (as a consumer). That'll allow a lot of existing Javascript components to be reused. For example: Microsoft Fast, Material Web Components and UI5.
-
List of Web Component libraries and systems
Material Design (Google)
- Material design on typescript without angular
spectrum-web-components
-
Making Web Component properties behave closer to the platform
For example, all the following design systems can be used without tooling (some of them provide ready-to-use bundles, others can be used through import maps): Google's Material Web, Microsoft's Fluent UI, IBM's Carbon, Adobe's Spectrum, Nordhealth's Nord, Shoelace, etc.
- I hate CSS: how can I build UIs?
-
Painless Web Components: Naming is (not too) Hard
sp- (Spectrum components from Adobe6)
-
Cypress component tests for Lit Elements (web components)
Spectrum web components by Adobe is really mature design system that makes a lot of usage of Lit Elements. Their testing setup uses the suggested web test runner. Lit's documentation on testing suggests using that library.
- JetBrains Ring UI
-
Exploring The F# Frontend Landscape
In Fable.Lit rather than building an F# DSL (we tried) we use a string-based alternative which is closed to the HTML you know and love, this also helps a lot when you have to consume web components like those from shoelace.style, fast.design, adobe spectrum components, and more, this will be a very important and big point over the next few years now that web components have taken off finally with major companies like Microsoft, Salesforce, Github, Adobe and more are using them.
-
Ask HN: Anyone know of any largish applications built with WebComponents?
Oh hey, that me! We at Adobe are investing heavily in web editors built with web component technology. Not just Photoshop, but Illustrator, Lightroom, and a number of brand new or in development applications across the company, as well.
We’re also leveraging web components to support interoperability of our design system across teams who still choose to use frameworks or have been using them all this time. In this way we ship https://opensource.adobe.com/spectrum-web-components/ and teams like fonts.adobe.com that have a long standing Angular app, or edex.adobe.com with their long standing Vue app or various recent acquisitions with their own technical decisions, can all consume Spectrum design without shipping their own implementation or rewriting their app to another stack.
The ease of building at depth scale for large applications and at breadth scale for applications no matter their architectural decisions has been a huge win for Adobe and our goals to drive consistency and quality across the company. The speed and scope at which we’ve been able to do so just wouldn’t be possible without web components.
-
Testing Accessibility with Shadow Roots
Recently, I had the opportunity to discuss the difficulties, learnings, and victories or developing Spectrum Web Components together with fellow custom element developers from teams at IBM, ING, SAP, and Vaadin. If you missed the live stream, check out the recording! Fellow panelist, Ari Gilmore, made a great point that there is a lack of reading material for developers like ourselves to draw from when looking to build solid accessibility practices into the web components space. With that in mind, I thought it would be a good idea to take some of the abstract concepts we discussed in the panel and share some actual examples of working and testable code. Hopefully, this can better support the next developer(s) looking to bring a high-quality, accessible, design system to life for their team via web components.
-
[AskJS] Javascript methodology/library/pattern for plain HTML Design System components
Their repos are public: - https://github.com/adobe/spectrum-web-components - https://github.com/adobe/react-spectrum
-
Who doesn't love some `<slot/>`s?
It does seem like I enjoy a good . I mean, look, I wrote about them all the way back in 2018 in ing in Some Tips, and then in 2020, I spoke about Stacked Slots at a virtual Web Components SF meetup (see the associated slides), before sharing a proof of concept for Light DOM as Model. And, as if that weren't enough, here we are again, and I'm writing to you, friend, about s. Today, we're going to get out of the theoretical and into the practical as we start on the path towards actual usage of Stacked Slots that I'm excited to bring to life as part of Adobe's Spectrum Web Components to support the delivery of Spectrum design's Help Text pattern.
What are some alternatives?
sycamore - A library for creating reactive web apps in Rust and WebAssembly
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME. WE ARE LIVE ON KICKSTARTER! 👇👇👇
lwc - ⚡️ LWC - A Blazing Fast, Enterprise-Grade Web Components Foundation
fast - The adaptive interface system for modern web experiences.
patternfly-elements - PatternFly Elements. A set of community-created web components based on PatternFly design.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
wired-elements - Collection of custom elements that appear hand drawn. Great for wireframes or a fun look.
silkenweb - A library for writing reactive single page web apps
vaadin - An evolving set of open source web components for building mobile and desktop web applications in modern browsers.
lion - Fundamental white label web component features for your design system.