Enable the “template” plugin.
Set “.obsidian\template” as the template folder, the plugin will say not found the folder even if it is exists.
Also, could you add “new with template” on right click content menu?
Thanks!
Also want this to be implemented for several reasons.
- To align file structure with other note management tools i am using from the terminal.
- To hide the Templates folder from the file tree.
I don’t agree that only .obsidian directory should be allowed to store regular and custom plugin templates. User mus be able to specify any hidden directory to store his templates.
I did just try this exact location. I think it’s very useful to keep things clean. Additionally using hidden folders automatically hides it from the node view.
I would like to see this as well. As a developer, I immediately tried to create and use a .templates directory and it took me probably 10 minutes to realize that (for whatever reason) a hidden directory just doesn’t work. The UI here around not being able to find the directory could really use some work, too.
The solution might easily be:
make folders with "."prefix only hidden for file browser.
I would also love to hide my attachments. All this stuff is hidden in a folder structure inside a “zzz” folder that at least sits on the very bottom of it all. But it’s far from elegant.
+1 for .templates (and hidden folders support in general).
Like @petergaultney, it is the first thing I tried when setting up my first template.
I’d happily contribute a pull request for this if I could. 
Did this get resolved somewhere? Has anyone found a way to get this to work?
When I saw that I needed a folder for templates, I immediately went to name it “.obsidian/template”, JUST like the OP. It appears that the the Core Plugin, Templates, can’t detect that or .templates.
I could be wrong, but I believe this to be an issue somewhere lower down than the Templates plugin because the file explorer also appears to ignore folders that start with a . (it doesn’t show them and if you go to create a “hidden” resource using the explorer, it automatically says you can’t. I think it would be more intuitive for it to allow the management of these resources and enable/disable hiding them in the explorer list, as this is how all the system tools handle dot files.
I was very surprised that .templates mysteriously failed to work until I changed it to a non-dotfile name. I don’t want to clutter up my daily Obsidian view with this rarely-accessed folder. If this is a product decision then an appropriate error message would save people time.
I get the impression that the developer team is not so familiar with certain database and file-management standards and best practices which others of us in the industry are used to. I’m hoping they are learning and making improvements based off of tickets like this and the life stopping sync errors we have been suffering (back your vault up with a git repo if you use sync or risk .. strange.. behaviors and sync issues).