Package revolution

[bouncepaw]

Currently, we store all HTTP handlers in one place, views in one place, their back-end models in one place. Used to do the same with localization, but I am currently bringing it closer to the actual views as part of #117.

I am starting to think that views and handlers should be in the same packages as their back-end friends. For example, the categories package. Or, the history packages. They would have everything inside and export only those things that should actually be stored. I expect it to be initialization stuff for many packages.

A good thing: this is 100 % architecture-only change, so users won't notice any difference during experimentation, which might take months.

[bouncepaw]

Reporting progress.

As of now, these modules got their own isolated packages with everything needed inside:

• Categories
• Backlinks
• Help
• Miscellaneous single pages

This is left:

• History
• Mutators
• Readers
• &c

Overall, I feel quite content with how it's all going. The number of inter-package relations reduces, making it easier to understand the codebase. A downside has emerged: there is a similar boilerplate in every such package. It's bearable.

I will merge the pkg-revolution branch. It didn't break anything (at least, I didn't find any new bugs), and the old and new template approaches co-exist ok.

This issue remains open until the revolution is done.