Who ever came to with this naming?
Spectre.css – A Lightweight, Responsive and Modern CSS Framework
131–135 of 135 posts
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#132Earlier quoted context omitted.
I've done frontend for quite awhile. I usually start with some sort of framework for every project and use only the minimal pieces for the foundation. Generally you need the same stuff for every site: - reset/normalize the styling cross browser - basic grid system - typography, forms, and buttons - "componentized" files with variables (sass, less, post css, etc) Basically I start with a custom build of whatever frame…
But is that grid system consistent across different sites? In my experience, I usually need to customize the "grid" to specific breakpoints and widths, as defined by designs/content. I find that it's often faster to just write a few helper classes for layout – specific to the site I'm working on – rather than use 15% of a framework's grid and still do heavy lifting. Of course, this isn't the case if the design team d…
For sure. Like I said, I usually do a custom build of a framework, then strip out the stuff I don't need. And if it's designed with variables, changing small stuff like breakpoints etc is maybe a few quick changes.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#133This will probably be a unpopular opinion but I think HTML should be fully semantic with a naming scheme for custom elements (not BEM, etc), take for example classic breadcrumb navigation, the element name would be to convey it inherits from HTMLUListElement so the actual structure isn't just an unknown mess of custom tags.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#134"Accessibility - coming soon"
This is not acceptable any more.
Re: Spectre.css – A Lightweight, Responsive and Modern CSS Framework
#135Earlier quoted context omitted.
IMHO Everyone should write at least one framework of some kind. Bonus if it's open source. It's a huge learning experience. Gives you a deeper understanding of how other other frameworks work. Helps you understand user and customer support. How to write documentation. Great for your resume. Etc. In other words, if you only ever consume frameworks it makes it difficult to know what to do or how to approach solving som…
Do you have any personal experience in doing so? They seem like tempting projects from the outset, but getting started with some clear goals in mind, alongside philosophical/idealistic differences from what's already out there so you're not simply rewriting something for the sake of it has prevented me from getting too far down a particular rabbit-hole.
Ah yes. Sorry this reply is so late.
My first php framework was something called php4gl back before ruby on rails was created. It used the command line to bake controllers and such. Just a private project never released. Lost the code now!
I also wrote another couple more php frameworks. I used one for all my personal side projects. And I wrote a couple for day jobs website over the years.
Actually it wasn't until Laravel came out that I was convinced NOT to write or use my own php framework ;)
So, now I've stopped writing php frameworks. But, I still write a CSS component framework from scratch for every project.
I wrote a really quirky javascript framework called Double Dollar that worked using a kernel pattern. Anyone I showed it to thought it was nuts. I abandoned it and now just use jquery for projects I work on like https://nugget.one
Probably the most sucessfull open source project I created was ezSQL. Wordpress ended up using it as their original database class and then as the API interface for their current wpdb database class. I think a lot of people probably curse me for that ;)