Introduction
The goal of this task is to refactor the current template system to use JSON files as the primary configuration source. Each JSON file will contain all necessary metadata and instructions required to configure the code generator.
This change is a foundational step toward building a Template Hub, where users will eventually be able to create, share, and download pre-configured templates.
Description

@
- Unified Information: Merge name and description into a single field, using the template name as an indicator of the frameworks used.
- Fixed Paths: Establish a fixed directory structure. All JSON templates must be stored in a specific folder to be loaded by the generator.
- The tabs indicate each part of the generated code being configured. This might not be user-friendly for a new user and seems to complicate things more than necessary.
- This part also doesn't make sense; it's as if you are only choosing the extension type for each template. All of these factors make it confusing to know what can or cannot be modified within the tool.
Ultimately, the ideal scenario is for this page to be just a selector for the templates the user has already downloaded, along with an option to download others. In the future, templates will have their own space to be created and edited; ideally, all of this should be hosted on an online page. Initially, it can stay on GitHub alongside the existing templates, serving as the defaults that come with the plugin.
Introduction
The goal of this task is to refactor the current template system to use JSON files as the primary configuration source. Each JSON file will contain all necessary metadata and instructions required to configure the code generator.
This change is a foundational step toward building a Template Hub, where users will eventually be able to create, share, and download pre-configured templates.
Description
Ultimately, the ideal scenario is for this page to be just a selector for the templates the user has already downloaded, along with an option to download others. In the future, templates will have their own space to be created and edited; ideally, all of this should be hosted on an online page. Initially, it can stay on GitHub alongside the existing templates, serving as the defaults that come with the plugin.