Settings naming

[JohnONolan]

Related to #11

I actually meant to raise a naming issue about this - potentially better as "blog" rather than "settings" ? as in blog.title or blog.logo or blog.globalthingrelatingtotheblog

Rename "settings" to "blog". We may have other types of setting exposed to the frontend soon.

[ErisDS]

If you like.. can get David to update his PR and I've not made the changes Ghost-side yet.
The only thing to keep in mind is that for the moment, it basically contains any and all settings from the settings table, although I intend to set a type.. which could be "blog" and then only provide settings of type blog to the theme.

[JohnONolan]

can we hold till tomorrow? (or update again tomorrow) - don't have a spare sec atm to go over

[cobbspur]

just let know when and what you want it to changed to... this i think i can handle lol

[JohnONolan]

@ErisDS Right - tell me more about this "type" thing?

[ErisDS]

So far settings have been key-value pairs. This is great but you end up with one big blob of stuff, and not all the settings are related.
I wanted to introduce a type field, so all settings are key-value grouped by type. It's a little more fiddly in some ways, but I think more powerful in others.

So, title, description, logo etc, all that would get a type of "blog"
Version, and other app fundamentals get a type of "core"
Stuff to do with plugins and themes might be "external" (this is not settings set by 3rd party plugins - thinking of having a separate table entirely for these)

[JohnONolan]

To clarify my understanding - 2 examples would be...

{blog.title} and {core.version} - right?

[ErisDS]

Something like that yep

[JohnONolan]

That's fine with me - so what do you want to do with this issue?

[ErisDS]

Updated & assigned.

[cobbspur]

so is this issue still open or you want to add the blog and core naming system, is there going to be a new type field ?

[ErisDS]

It requires/ is waiting on TryGhost/Ghost#172