Cover Photo by Kelly Sikkema on Unsplash
But Why?
Ok, thats a Funny story. But, first of all, here is the link in case you are curious ...
For further actions, you may consider blocking this person and/or reporting abuse
This is nice! There's a bit of inconsistency though. The meter and progress seemed off compared to the rest. I'm using Firefox. Here's the screenshot: gyazo link
Uow, thats true. What firefox version? I tested with the last one. Also, meter and progress are hard to style natively, and all components are directly styled, there is no opinionated architecture or imposed html structure to build fake elements. This is not wrong of course, but this framework is just not intended to that. Meter and Progress are styled using vendor prefixes, maybe your version doesnt support those vendors yet, ill wait to know about which version are you using and try to figure out if has a workaround. Thanks for your feedback :D
I'm using Firefox 76.0.1 (64-bit). It looks okay on Chrome though. So yeah I think it doesn't support it yet D:
True. I'll download your version and try to figure out a solution. If all fails, maybe offer a workaround with spans. Thanks again.
Hi Felippe,
Awesome post and a cool project. The idea to scope it is soo important for adopting the styles.
Two questions are spinning in my head:
why did you decide against Miligram and Skeleton in the first place
how would you compare plume vs something like MVP.css
Hey! Thanks for your comment!
Skeleton and Milligram are micro-frameworks that i use to fast-build small projects. As there were some points there i would like to be different and i were already experimenting different styling approaches, they automatically became an inspiration.
I didnt know MPV.css. Looks great! MVP.css sure will be a reference for the future. I want a no-classes frameworks by default too, just semantic HTML. MVP seems more mature in this point. I think that the main difference is that Plume is Scoped (as you pointed), but i assume thats easy to achieve with MVP.css. Plume has a larger set of elements styled, also with more consistence (at a first sight): andybrewer.github.io/mvp/mvp.html. The available props to customize are easier to tune on MVP, but Plume seems more complete at this point, but at here i think is more about taste: do you want props or do you want to override selectors? Despite the semantic approach, Plume's also has a nice set of utilities. But at the end, i think its all about your taste and needing. MVP seems really great.
Great work! I can see the
plume.cssis a component-based framework. Waiting for your new component collection soon. You earned a star at Github, from me.Yes, i have a solid plan to write a "plume components-js" lib also with a simple set of plume-based components using JS web components to encapsulate complex behaviors. Many thanks Loouis :D
I just wrote an article about my experience trying out Plume. Spoiler alert: I love it! So simple, but very powerful. Amazing job!
Also, now that I've randomly stumbled into this article and got to read about the backstory, I love it even more. 😄
This is neat! I like the style you used, gonna star this on github so I can go back when I need to create a web using this style. Thanks!
Thanks Made! Take a look on the bottom left button on the project github page, its a menu with some custom themes to toggle that you might also like ; )
Nice work. Plume- css seems too promising. Please add datatable ui ... search indexing etc
Would be cool to build some components based on Plume style. But implement a datatable or search indexing i believe it would be problematic since Plume is a pure CSS lib
Can you disable the scoping?
Hello Ben, yes its possible. You must clone the Gihub Repository, then in the file "plume.config.js" you must set the { superclass: ... } to "" and the { prefixer: ... } to false. Then run:
npm install
npm run build-all
By doing this, styles will be applied on body instead of the "plume" class (or one designated by you), and the selectors wont be prefixed.
That's amazing job! Very interesting! I will test it!
This looks flexible enough that I could see myself use it next time I start a project from scratch.
That, and it seems to work like a "regular" CSS framework.
Well done!
Many thanks Mikael! Happy to read that. I thought a lot about if this is a framework or a micro-framework, but there is no grid-system (as a choice), no optionated architecture, no components (cards, menus, sidebars, etc). At the end its just pure and native HTML elements and CSS. A framework for those who like to code the things from scratch, maybe? So i called a micro framework (but i dont know), and yeah, its a pretty complete one haha.
Congratulations! You did a great job.
uow, thank you Chan!
Nice job. Love the style. This might be the first "framework" I've been excited about in years. Will have to give it a whirl!
Nice to hear that Derek. Hope it can be useful for you! Have a nice code!
Hey Felippe, this looks really cool and am keen to try Plume out, thanks for the really insightful article.
Hey, thank you Nick! :B
Awesome I like it.
BTW have you checked chota css?
Thanks Shriji! Yes, i didnt implemented Chota, but i saw the documentation and the sources as a brief reference also. Seems really nice : )
This is awesome <3 Especially the date and time inputs. Looking forward to contribute!
Thanks Suvin!