Update docs.md

[markbrewster]

No description provided.

[newkind]

I'd add 2 modifications to thie PR.

1. Change the BLOG_NUMBER to the SITENAME-ID as BLOG_NUMBER can be confusing and misleading if someone uses different name than BLOG

2. Add information that each custom.scss will be available only for the site that this particular custom configuration belongs to.

[markbrewster]

Thanks for the suggestions @newkind I have amended the copy.

[newkind]

@markbrewster Thanks for the updates.

@mahagr One more question for you here. Can you please check in the code if having a multisite installation means that Gantry 5 will always look for custom.scss only under custom/SITENAME-ID/scss/ or both locations custom/scss/ and custom/SITENAME-ID/scss/ ?

It really should do both in this case, so you could have global custom.scss and per site custom.scss.

[mahagr]

I believe that custom folder is used only from the current template, mostly because of configuration is stored in there and it would be confusing that changing parent configuration or layouts also changes them from the child theme.