Document file template
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=394841) </details> <!--IssueSummary end--> <!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve <!-- Include the following detail as necessary: * What product or feature(s) affected? * What docs or doc section affected? Include links or paths. * Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs? * Any other ideas or requests? --> We have a hole in our docs here, for talking about file templates in general. - https://docs.gitlab.com/ee/user/admin_area/settings/instance_template_repository.html is about setting these templates at an INSTANCE level, and mentions gitignore files. - https://docs.gitlab.com/ee/user/group/manage.html#group-file-templates is for GROUP level templates. - https://docs.gitlab.com/ee/api/project_templates.html, https://docs.gitlab.com/ee/api/templates/gitignores.html, https://docs.gitlab.com/ee/api/templates/gitlab_ci_ymls.html, etc are API documentation. The first two above are more for admins. The latter are for developers. There is no basic page for users that ties all these concepts together. When you add a new file and type in the name of a template file you get additional options like, e.g. for .gitignore ![image](/uploads/56ee3f3b9d2c88c8a249fb0525987008/image.png). But you have to know that this is available. For some file templates there is a button on the project main page but not on the repo->Files page: ![image](/uploads/5888ee694e3b36aa2661d99598170620/image.png) ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?subscribed=&search=persona%3A --> ### Proposal <!-- Further specifics for how can we solve the problem. --> * Definitely fill this gap in the documentation (maintenance; this issue here) * Consider improving the discovery (feature; to be considered; create separate issue in case we want to do this) ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> Documentation team ### Other links/references <!-- E.g. related GitLab issues/MRs -->
issue