sounds good.
And the reason for keeping with zone's structure of config_example.json and website_example is when you do a git pull it pulls the new files. If you don't do this then the files wont download and need to be merged prior since they have been changed.
The source files in /lib might have dependencies on new /config.json & /website. That is why you should not pull just a part of the source code but rather merge the full repository instead.
were talking about different things.
if you keep them all with _example pool ops can do a git pull then modify all the files that changed, makes it much easier.
I am sorry, but I think I have to disagree. If you check most popular open source projects, you'll notice that 90% of them do not use any *_example postfixes for config files and 99.99% do not use _example for directories.
We just wanted to make pool installation and update as easy as possible. That implies that pool ops do not have to worry about every single update doing merge in manual mode. I am not sure if all pool ops are such good programmers.
Anyway, if you want *_example source code version, you can just do a fork of CUP repo, rename website -> website_example & config.json -> config_example.json in forked repo, and then use next commands to sync your repo with CUP repo:
git remote add cup https://github.com/fancoder/cryptonote-universal-pool
git pull --all
git merge cup/master
By the way, I've added a link to extremepool.org to
https://github.com/fancoder/cryptonote-universal-pool#pools-using-this-software