What is the Veams Methodology?
Veams Methodology refers to how Veams projects are structured and built up for modularity, scalability, and maintainability.
Most web development methodologies are only scoped to
CSS. As a result, they only handle
class systematics. Veams is scoped to
Veams Methodology does not reinvent the wheel. Veams Methodology is based on concepts from BEM, frontend development, backend development and extensive feedback from professional web developers.
What differentiates Veams’s Methodology from other web development methodologies?
Veams is a methodology that you can apply across your entire frontend stack.
Typical questions which Veams Methodology is answers are:
- How should you scope and differentiate your
- How should you bind
- How should you structure your layouts?
- How should you write your
- How should you expand your project?
Instruments To Structure Your Markup
Markup in Veams applications is structured using “instruments”. In the context of Veams instruments are tools that you will use to structure the pieces of your application into one of three categories:
Every instrument has a specific purpose and unique attributes. Click the links above to learn more about each instrument.
CSS class writing system
In general, Veams class naming includes 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
Despite that Veam’s class naming convention is based on BEM – Veams does not use BEM. Veams uses BEM with restrictions how deep your class names should be. To learn more about how Veams flavor of BEM visit the CSS Introduction Introduction section.
Veams Methodology uses