Deep rebranding in v5

[peterpp]

One important note about rebranding. In v5, I would like to rebrand also the source code and internals as well. This will affect a namespace, core classes, cookies and compiled filename. If you already use v5 (and I am really glad if you are), brace yourself for impact.

[iamdabe]

keeping a keen eye on this! This is exactly the tool I need, so glad you're working on it!

Looking forward to the docker-compose setup as that's what my environment is!

Thanks for all your hard work!

[peterpp]

Rebranding is prepared in deep-rebrand branch. For those who have enough courage 😉

I'm a little hesitant about naming the main class just Admin. But we have a folder admin, function admin() and variable $admin. So it is consistent.

On the other hand, main creation function is called create_adminneo(). It will be typically defined without a namespace, so it is better to have a unique name.

[adrianbj]

Well it took a bit to get things up and running again (mostly plugin class names and the change to the neo_permanent cookie), but with those done, so far, so good!

[peterpp]

Wow, you are fast 😲👍

I also want to rename plugin files to match the new class names. I will do this along with their revision.

[peterpp]

Rebranding is finished and merged into the version-5 branch. I also replaced the sign <? in logo. I hope you will like it 😉