An important lesson in being rigid about staying flexible, our previously announced name for this module is making people think its unneeded.
It seems I have missed a trick with branding! After meditating a lot on this, and meeting with a few people about it, I have decided to change the name of our First Champion Module from yourFrontend to yourBackend.
If anything, it might make people pay attention a bit more - after all we seem to have a lot of front-ends around HIVE - but how many backends do we have? The only one I know about it 
So let's try to grok it together. Stop looking at the front end. Yes we could have spent 15 hours stripping down someone elses javascript code. Instead we spend 7 hours putting together exacly the ENV vars we needed for:
Yes of course I am promoting open source, but wordpress does not require repository forking or code editing. It is also not built entirely of javascript, I should mention. It has a LAMP stack. You can decide where you think HIVE fits into the LAMP, but does it really matter?
I asked 
"yourFrontend" page feature, rapidly and efficiently created by 
Configuration Management
To streamline the configuration of yourBackend, we've developed a Flask application that provides access to user settings stored in MongoDB through a fast, straightforward API.
Each instance we deploy is a complete, self-contained git clone of the repository with full configuration capabilities. This architecture allows for efficient management through API calls while maintaining flexibility.
As an open-source project, YourBackEnd can be configured without using our API service. Users can either edit the settings file manually or utilize the included configuration builder application.
All instances are served using Caddy, which simplifies deployment with automatic SSL/TLS certificate management. Caddy can be configured without directly editing the Caddyfile. We have plans to further automate the provisioning system for the instances we host.
Its not a wallet, you can't find your friends, you can't write a snap or a post. No one can use your domain to randomly append to the url and find someone elses content on HIVE.
It would be quite unprofessionally for a corporate domain to accidentally show something on someone else's post wouldn't it? yourFrontend yourBackend give you CONTROL! over what is seen. Without forking anybody, especially not the hardworking teams building out important frontend options for our HIVE chain.
Special Thanks to 
And also, thanks to 
Sidebar: I didn't mention in our official DHF support staff list, but @kit.andres is my docker guy. He keeps busy nowadays dockerizing processes for big companies around latin america, but I onboarded him in 2018 to work with me on @coffeesource.net and he was also the one I tapped to help @josephsavage build the https://www.hivesbi.com and api.
If I needed help Redhat-ing a docker process, I would call him first.
I think both of these frontends have great and powerful use cases. I am fascinated by the idea of offering a B2B Microservice for both, they are different.
I see what is being built. I like these people, and I consider that their work is not in vein - I see (great and powerful) usecases for both frontends mentioned above. I hope to consider every builder on HIVE a friend - but I definitely know them to be allies.
And something tells me, they are going to be reaching out to me when the first customer says "lol wut? you want me to fork what?"
So once again I am asking for your scathing criticisms. 5 HBD bounty for the first one that gets me the Bernie.gif with this amended text okok.
Simplest Vision - RedHat of HIVE
Champion Modules
If you are having lots of fun along with us, don't forget to click that 
