Talk brainstorming

SMURF - Scalable, Modular, reUsable Rails Frontends

THE Problem

"Frontend code sucks!"

• most definitely for LARGE web applications

• inconsistency!

  • file structure
  • naming
  • UI

• tight coupling (Markup + CSS & JS)

• no single-responsibility

• unclear responsibility

• unclear applicability

Beyond the code 1

• Page mentality

Beyond the code 2

• Disconnect between designers and developers
• form vs. content
• problem of language, naming and communication artifacts

Beyond the code 3

• inconsistent UI

THE solution

• well, OK, maybe more like part/beginning of a solution

Outline:

• classes instead of IDs (for CSS)
• the "Semantic" Markup Myth
• stop the cascade - limit depth of applicability
• file structure
• naming conventions for Sass variables
• Smurfville