When I first started building (b)log–In it was only ever intended as a personal project and this influenced a number of design decisions – read as taking shortcuts. One such choice was the site name which is currently defined as a constant rather than being saved as an option in the database.
A constant is as a constant does – there's a reason they're called constants after all. The site name is currently static, unchangeable unless you want to manually edit config.php
But the idea with the system is that you don't, or shouldn't, have to do that kind of stuff.
Opening the platform up to others has made me realise that certain features need to be a little more flexible so I will have to rework a number of things. Making the site name changeable will mean adjusting the setup process, the admin page, the blog page, footer, RSS feed generators, and just about every other page. Not such a minor undertaking, but it will be worth it in the long run.
@colinwalker I'm a big fan of having stuff that rarely change in a config file to avoid having a lot of database queries all over
I mostly agree but some things need to be configurable. There's still a bunch of constants in there, this will just be one less.
@colinwalker Configurable doesn't mean there is a GUI for it.