Login, forgot password, signup and other tpls...
Design and Skin Customization
It can be confusing as to why there are multiple locations to edit stuff. Here's a short 'why'.
In the beginning Jamroom was not editable by the end user, there was no way to extend it without asking for a feature. It was also only for music websites. With version 4 (I think) we got a way to add modules to extend the ability of the system. Making a module meant building in php and uploading via FTP to your server.
With jamroom 5 the architecture changed to make 'jamroom' just a core set of modules of which even the core was a module of itself. Skins became a way to take advantage of the modules that existed in the system. So if you built a skin you might make it general and able to use ANY module or you might make the skin require X modules and not work with some modules. How the site looks is pretty much controlled by how the skin designer chose to build.
To allow the skin designers a way to customize things like the login page 'template overrides were added'. That meant that a skin could take the template a module used and copy it to the skin, then the system would prefer that template over the one the module has. ie jrUser_login.tpl.
Docs: Altering a modules template
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1051/altering-a-modules-template
That flow worked well for a while, and is still the flow that most developers will use as it allows for module updates without needing to re-add the changes.
Then the request came in from non-developers to be able to make 'just small tweaks'. The system built for them was the TEMPLATES tab in the ACP in the MODULES and the SKINS section. Its supposed to be a one-or-the-other setup but if you use both it can be really hard to figure out if where the over-ride is.
