Why Another Methodology?
There are many frontend methodologies out there. And I like a few of them. But I don't feel comfortable with them at all.
Most methodologies are scoped to
css. To be more specific, these methodologies are only handling
class systematics. But I think that is not enough.
So I decide to go my own way of structuring projects.
I am not reinventing the wheel. I just take out some pieces from BEM, take some parts from my backend experience (mainly Drupal development) and frontend expertise in various projects and get important exchange through the close dialogue with other developers.
What Is The Difference?
Veams-Methodology is a system for your whole frontend stack. Typical questions - which Veams-Methodology is solving - are:
- How to scope and differentiate units (Components, Blocks, Regions) in your
- How to structure layouts?
- How to write your classes?
- How to extend your project?
Instruments To Cluster Your Markup
Veams-Methodology uses specific instruments to structure your web application. In general it splits up your project in four main instruments. These are:
- Regions (in layouts)
Every instrument has specific attributes.
data-attributes which are graduated in:
- Module initialisation (
- Options handling (
- Event handling (
Of course it makes no sense to use this part of the methodology when your application involves a framework which is already using declarative bindings.
In short Veams-Methodology integrates the following:
- BEM similarities to scope styles
- Prefix usage to differentiate between instruments
- Global Styles for instruments
- Modifier and context styles
- Layout styles with Regions to separate concerns