Merging the Shine project with the Glowstone site

Hello all,

we have been thinking about merging this project (Shine, the plugin database) with the [new Glowstone site](https://github.com/GlowstoneMC/Site). The site's server software is made in Python, but already has an excellent base for development of new features. It has entered production mode earlier this week and now replaces our old Github pages site.

Instead of rewritting a website engine in a different language (currently Node.JS here), and having to re-do most of the designing of the front-end to match the current site, I think we should make Shine *part of* that server software.

The Glowstone site already has accounts (although no public profiles) and a template rendering engine, API engine and other features. Instead of re-inventing the wheel, maybe we should consider this an option.

Please reply if there are concerns about this option or other questions!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/49303230-merging-the-shine-project-with-the-glowstone-site?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github).

The issue proposes merging Shine with the Glowstone Site, whose server software is described as Python-based, while Shine is described as Node.JS. Start by reviewing the Glowstone Site linked in the issue and comparing its accounts, template rendering, and API features with Shine; the issue does not name files, tests, or a concrete definition of done.

Written by the indexing model from the issue text.