Switching to another methodology

[moeenio]

The project uses the BEM CSS methodology, which makes classes follow a block__element--modifier pattern, where (quoting from the website):

• block "Encapsulates a standalone entity that is meaningful on its own. While blocks can be nested and interact with each other, semantically they remain equal; there is no precedence or hierarchy."
• element "[are] parts of a block and have no standalone meaning. Any element is semantically tied to its block."
• modifier "[are] flags on blocks or elements. Use them to change appearance, behavior or state."

Alternatives are :

• SMACCSS, which splits the CSS into categories : Base, Layout, Module, State, Theme
• SUITCSS, which uses both utilities and components
• Atomic CSS, which "like inline styles, offers single-purpose units of style, but applied via classes."
• Object-Oriented CSS

Do you prefer any other than BEM @Scratch-Client-4/frontend ?

[micahlt]

@locness3 Ah, sorry, thought @Hexsphere already stated this, but we're using BEM.

[moeenio]

ok

[moeenio]

Reopening so @Scratch-Client-4/frontend can suggest if they prefer something else

[VFDan]

Which one does Scratch use?

[moeenio]

I'm not sure, I feel it depends on the page (project page, other page, or page that is in the old "style").

But I'm not sure Scratch is a good example to follow IMO

[ethanhanderson]

@micahlt I was only suggesting tools that I used. I think once we're ready to start coding we should make sure everyone's on the same page as far as what frameworks, methodologies, and architectures we use

[micahlt]

@Hexsphere Ah, okay. Gotcha. I still support BEM, as it looks like it's the easiest to use and read.

[VFDan]

I think BEM would be the best.

[micahlt]

Haven't heard from anyone else- everyone good with closing this issue and staying with BEM?