Styling Frameworks.

Introduction

During an expert interview with the chapter lead, one important thing that came up was the need for the tool to be as independent as possible. The chapter lead said for example that the tool should not rely on any single styling framework like Tailwind for the page's styling. Instead the tool should be flexible and allow users to choose their preferred styling framework. This would make the tool more appealing to a wider range of users.

Abstract

To achieve the goal of making the tool more independent, I added a functionality that allows users to select a styling framework. This feature can be expanded in the future to include more styling options. For now I included two options: no framework (standard CSS) and Tailwind. By adding a dropdown menu to the options within the tool users can now easily select the styling framework they want.

On the backend I had to make some adjustments to make this new feature work. I added a new set of prompts that get triggered if the Tailwind option is selected. This makes sure that the tool generates the correct styling code based on the user's choice. By implementing these changes I made sure that the tool could support different styling frameworks without breaking the functionality. When a new framework needs to be added, all that needs to be done on the backend is to change "tailwind" to a desired framework name.

Conclusion

This new feature increases the flexibility of the tool. Even though Tailwind is a popular styling framework, many users still prefer using standard CSS. So giving users the option to choose their preferred styling method makes the tool becomes more user friendly. The tool is now better in meeting the need for various styling frameworks which makes it a more usable option for end users.