{"id":27993,"date":"2019-09-17T21:29:16","date_gmt":"2019-09-17T13:29:16","guid":{"rendered":"https:\/\/www.hongkiat.com\/blog\/?p=27993"},"modified":"2022-10-08T17:11:11","modified_gmt":"2022-10-08T09:11:11","slug":"web-dev-acronyms","status":"publish","type":"post","link":"https:\/\/www.hongkiat.com\/blog\/web-dev-acronyms\/","title":{"rendered":"30 Acronyms All Web Developers Should Know"},"content":{"rendered":"

The jargon of the web development industry contains so many acronyms<\/strong> we are using day in and day out, that it\u2019s not only daunting for novices, but sometimes also hard for practicing developers<\/strong> to follow<\/strong>. Most of us safely use more common acronyms such as HTML<\/abbr>, CSS<\/abbr>, or HTTP<\/abbr>, but what about the less widely used or newer ones?<\/p>\n

In this glossary, we have collected 30 acronyms that are frequently used in today\u2019s web development articles and discussions in order to help our readers keep up with the contemporary industry lingo<\/strong>.<\/p>\n

\n\t\t\t\t\tRead Also:<\/strong>\u00a0\n\t\t\t\t\t10 Numeronyms Every Web Developers Should Know<\/a>\n\t\t\t\t<\/p>\n

1. ARIA<\/h2>\n

Accessible Rich Internet Applications<\/em>: sometimes also used as WAI-ARIA<\/abbr>.<\/p>\n

Web standards<\/a> published by the World Wide Web Consortium<\/a> (W3C). The ARIA specification defines different front-end methodologies<\/a> that make web content accessible for disabled people<\/strong> who access the web with assistive technologies (AT), such as screen readers.<\/p>\n

\n\t\t\t\t\tRead Also:<\/strong>\u00a0\n\t\t\t\t\tA Look Into: ARIA Web Standards & HTML Apps Accessibility<\/a>\n\t\t\t\t<\/p>\n

2. ACSS<\/h2>\n

Atomic Cascading Style Sheets<\/em>: a CSS writing methodology developed by Yahoo.<\/p>\n

ACSS<\/a> is based on reusable, single-purpose (Atomic) classes<\/strong> and short, predictable class names<\/strong> that make it possible to style directly the HTML. Atomizer<\/a> is a tool that can help generate Atomic classes for web projects.<\/p>\n

Recommended Reading:<\/strong> The Basics of Object-Oriented CSS (OOCSS)<\/a><\/p>\n

3. AMP<\/h2>\n

Accelerated Mobile Pages<\/em>: a mobile web standard initiated by Google with the purpose of making mobile sites faster<\/strong>.<\/p>\n

AMP<\/a> restricts how we can use HTML, CSS, and JavaScript in order to improve performance, and it provides us with Components<\/a> we can use to load external resources and run scripts via the AMP runtime<\/a>.<\/p>\n

Recommended Reading:<\/strong> Beginner\u2019s Guide to Accelerated Mobile Pages (AMP)<\/a><\/p>\n

4. API<\/h2>\n

Application Programming Interface<\/em>: a set of pre-written code features<\/strong> (properties, methods, classes, etc.) specified by the publisher of the API, that help us use best practices<\/strong> and write consistent code<\/strong>.<\/p>\n

We can choose from many web APIs<\/a>, but social media and technology sites, such as Facebook<\/a>, Twitter<\/a>, and Google<\/a> also publish their own APIs.<\/p>\n

5. BEM<\/h2>\n

Block, Element, Modifier<\/em>: a naming convention<\/strong> for writing readable, consistent, and maintainable CSS classes.<\/p>\n

When using the BEM<\/a> methodology, we create classes throughout the whole project that follows the block__element--modifier<\/code> syntax<\/strong>.<\/p>\n