search

davidhund / objecss.com

Collection of tiny, reusable OOCSS (Sass) objects and Sublime Text snippets
2 stars 0 forks source link

Start over #1

Open davidhund opened 9 years ago

davidhund commented 9 years ago

Simpler now. Simply create a forkable repository of basic OOCSS 'objects'. No Sublime Text snippets, etc. No 'CSS framework' (styling).

'Objecss'

An 'Object' is a structural, re-usable, OOCSS component. Think of:

wjthomas9 commented 9 years ago

Hey there. I recall this from a while back when I was doing something similar. Happy to pitch where I can as you establish direction. I also have objecss.io if you're ever interested in using it.

davidhund commented 9 years ago

Ha, that was quick :laughing:

I was just reminding myself I had these plans. I still think there's some value in an online repository of reusable OOCSS 'objects'. There's enough 'frameworks' out there, but I (and I believe many others) have a need for robust and reusable CSS objects that can be dropped in any project.

What are your thoughts? I was thinking of starting very(!) small by simply starting a(Jekyll/gh-pages) listing of 'Ojecss'. That's it ;)

PS: My personal preference would be to have them as .scss files: this way one could easily @import them or—when not using Sass—copy the compiled CSS.

wjthomas9 commented 9 years ago

I completely agree on both starting small and using Scss. I had so many grand ideas before, but starting small is probably the most realistic. ;)

Have you put any thought into using something like BEM to name classes with?

And do you think it’s worth considering adhering to Stubbornella’s OOCSS principles? https://github.com/stubbornella/oocss/wiki

On Nov 18, 2014, at 2:01 PM, David Hund notifications@github.com wrote:

Ha, that was quick

I was just reminding myself I had these plans. I still think there's some value in an online repository of reusable OOCSS 'objects'. There's enough 'frameworks' out there, but I (and I believe many others) have a need for robust and reusable CSS objects that can be dropped in any project.

What are your thoughts? I was thinking of starting very(!) small by simply starting a(Jekyll/gh-pages) listing of 'Ojecss'. That's it ;)

PS: My personal preference would be to have them as .scss files: this way one could easily @import them or—when not using Sass—copy the compiled CSS.

— Reply to this email directly or view it on GitHub https://github.com/davidhund/objecss.com/issues/1#issuecomment-63534927.

davidhund commented 9 years ago

Yes: Nicole's principles are great guidelines. But there could be many more. I too am a fan of BEM.

However, I feel we could approach this pragmatically also: maybe set up some 'guidelines' regarding robust (S)CSS—nesting, specificity, overly qualified selectors, that kind of stuff—but not be too restricting.

I would not want to alienate FE's who, say, do not like BEM. This will probably work itself out. Maybe the Sass objects could all start with some $object-name: foo; variable, so that we can have some flexibility in naming them...

I'm rambling: what I mean to say is, let's start and worry about 'principles' when we run into issues with them ;)

wjthomas9 commented 9 years ago

I’m a fan of BEM as well, but I admit, I rarely use it, especially on smaller, simpler projects. I do tend to name my classes in some sort of similar fashion, even if I don’t follow their exact syntax. So, I agree with your suggestions.

And, I would probably suffice to just link to or create initial awareness of Nicole’s principles. I certainly don’t want to re-invent that wheel on another repo. ;)

On Nov 18, 2014, at 2:18 PM, David Hund notifications@github.com wrote:

Yes: Nicole's principles are great guidelines. But there could be many more. I too am a fan of BEM.

However, I feel we could approach this pragmatically also: maybe set up some 'guidelines' regarding robust (S)CSS—nesting, specificity, overly qualified selectors, that kind of stuff—but not be too restricting.

I would not want to alienate FE's who, say, do not like BEM. This will probably work itself out. Maybe the Sass objects could all start with some $object-name: foo; variable, so that we can have some flexibility in naming them...

I'm rambling: what I mean to say is, let's start and worry about 'principles' when we run into issues with them ;)

— Reply to this email directly or view it on GitHub https://github.com/davidhund/objecss.com/issues/1#issuecomment-63537454.

davidhund commented 9 years ago

Maybe start with a simple collection (.md?) of objecss. Then work on a 'format post' (for jekyll)?

wjthomas9 commented 9 years ago

That sounds nice and easy.

On Nov 18, 2014, at 3:28 PM, David Hund notifications@github.com wrote:

Maybe start with a simple collection (.md?) of objecss. Then work on a 'format post' (for jekyll)?

— Reply to this email directly or view it on GitHub https://github.com/davidhund/objecss.com/issues/1#issuecomment-63548130.

davidhund commented 9 years ago

Start: https://github.com/davidhund/objecss.com/wiki

wjthomas9 commented 9 years ago

Sweet!

On Nov 20, 2014, at 4:29 AM, David Hund notifications@github.com wrote:

Start: https://github.com/davidhund/objecss.com/wiki https://github.com/davidhund/objecss.com/wiki — Reply to this email directly or view it on GitHub https://github.com/davidhund/objecss.com/issues/1#issuecomment-63788707.