# Generic Overview

It showed how to set up a proxy configuration and also how to use the playground feature in order to explore components, layouts, panels etc. Furthermore, it discussed creating new features by using a copy paste approach and explored what purpose is served by the API TS file for development purposes.
The back end development team will create a copy of the repository and push it to a certain branch. The front end developer can then pull that branch, work on it locally, commit changes, and then create a new merge request in their remote GitHub. They should assign the request to Joseph Maria or Victor depending on whether it is for back end or front end code respectively. For creating a new component after login, there may be some additional configurations required if authentication is involved; however, no permission from Creologix or Ldira is needed. Lastly, they need to follow the naming convention as specified by the front-end standards when committing changes so that they appear in their remote folder with their brand.
The speaker discussed how to use the Jira Tool tracking system. They described the process of creating a ticket with a description, assigning labels and JIRA link, and submitting a merge request. The speaker also provided instructions on running commands in the front retail folder to test desktop or mobile applications.