## Background Follow up from the discussion in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/88058#note_954132433 Miguel: > `@ekigbo` thanks for this change! Code-wise LGTM! Do you know if we have any feature specs to prevent this regression in the future? Ezekiel: > Thanks @mrincon for the quick review, that's a good question, i didnt come across any related tests and i'm not too sure how we'd test this scenario apart from perhaps a feature test that goes through and selects every template on the page :thinking: > > Interestingly this data is kind of duplicated, its on both the [~backend](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/project_template.rb#L45) and ~frontend and i'm not entirely sure _why_, so i think a better solution would be to only rely on the ~backend data and add the ~frontend key to the data there. ## Implementation guide * Remove https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/projects/default_project_templates.js * Use a `data-*` attribute to bootstrap the template [data from the backend](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/project_template.rb#L43) * Note: there are some EE only templates too * We should udpate the ~documentation for [updating templates](https://docs.gitlab.com/ee/development/project_templates.html#create-a-merge-request-with-vendor-details) to reflect any changes made