Yes it does, and I have tested with multiple themes, all work.
I have also created a new site and repository and started the process all over with a new theme, and that too works very well on my system.
It is just when deploying to Netlify they all fail, with the error message Error: Unable to find theme Directory: /themes/XXX, XXX being the theme directory and name.
And also, “Error running command: Build script returned non-zero exit code: 255” which I understand is not using the correct Hugo version, but I started using netlify.toml, so that shouldn’t be an issue.
In config.toml try either removing the themesDir setting (I don’t think you need it since you’re using the default location) or setting it to themesDir="themes" (remove extraneous /'s).
I would just remove the unnecessary settings… less things to debug. Also as @funkydan2 noted, that path is wrong… it is beginning with a “/”, which implies an absolute path. But in any case, simply removing it is better.
Add only the settings that are needed for your site to build.
So the main culprit seems to be that typo in either the actual theme dir name, or the theme name in config.
Yes there is. Right next to the message in your dashboard that the deploy failed, where you got the quote of the error messages, right there is a button that connects you right with the support.
Honestly, I have always copied the archetypes and the config.toml from the theme itself. But I did try removing it, like you suggested, but it did not work.
Update - Issue sorted, thanks to support from Chris over at Netlify.
His solution was to use submodules (seemingly mine was set up incorrectly) or delete the .git subdirectory from the theme directory which would ensure the theme was uploaded. Obviously this means that I have to update the theme manually, but something I can live with right now while I’m still learning Hugo and Github.