Using Dynamic CSS Classes in the Hand Talk Plugin

What is dynamic class generation, and what is a class?

A CSS class is a concept used in web development to style elements of a page. It is a set of rules that describe how an element should be visually presented in the browser. For example, we can create a "button" class that defines the color, size, font, and other visual attributes of a button on our site. This class can be applied to any button on the page, allowing all buttons to have the same appearance. It's like the class is a template for an element's appearance, and we can apply it to multiple elements so that they all follow this template.

Dynamic class generation is a technique where classes are automatically generated instead of being predefined in the source code. This allows classes to be created based on the needs of the Hand Talk Plugin.
 

Why do we use dynamic class generation in the Hand Talk Plugin?

We use dynamic class generation to avoid conflicts on client sites. This is because, in many cases, sites already have their own CSS classes defined, and if the plugin uses the same classes, it can cause conflicts and interfere with the appearance and functionality of the site.

With the use of dynamic classes, it is possible to change the appearance and style of the Hand Talk Plugin without affecting the client's site components.

Other advantages of using dynamic classes include reducing conflicts with other plugins and the ease of code maintenance, as the classes are generated automatically according to the plugin's needs.
 

Why is it not recommended using the plugin's component classes to change their styling?

Although it is possible to use the plugin's component classes to change their styling, this is not recommended because new dynamic classes are generated with each plugin update, which can break the client's changes.

Additionally, the visual design of the Hand Talk Plugin is designed for optimal usability for deaf users. Altering the plugin's styling can negatively affect its usability and accessibility, compromising its primary function.

An example of this would be a situation where a client creates a custom button for the Hand Talk Plugin within an accessibility toolkit by manipulating classes in the DOM. Although this solution may initially work, with each plugin update, new dynamic classes are generated, which can break the client's logic and compromise the plugin's functionality.