Would it be possible to add several predefined color schemes to the settings for a template, supporting Customizer?
Seems to me it's loading colours from default customizer.json, no-matter which colors it's in the default css.
Anyhow I would really like to see the designers docs being extended by someone knowing the full potential of the system, e.g. how to add settings etc.:
https://arastta.org/docs/designers/customizer
Seems to me it's loading colours from default customizer.json, no-matter which colors it's in the default css.
Anyhow I would really like to see the designers docs being extended by someone knowing the full potential of the system, e.g. how to add settings etc.:
https://arastta.org/docs/designers/customizer
In Themes
Share this post:
Accepted Answer
Hi Rune,
Thank you for the suggestion. Having "pre-defined styles" and color pallets what I also want to have in Arastta. But it would be better if we have a css preprocessor, like Scss or less. Thus, we can implement pre-defined styles much more easier and also developing a new Arastta theme will be a joy for designers.
So, let's follow up this and have in the future Arastta releases.
I just updated Customizer documentation and now you can find more instructions there.
Regards...
Thank you for the suggestion. Having "pre-defined styles" and color pallets what I also want to have in Arastta. But it would be better if we have a css preprocessor, like Scss or less. Thus, we can implement pre-defined styles much more easier and also developing a new Arastta theme will be a joy for designers.
So, let's follow up this and have in the future Arastta releases.
I just updated Customizer documentation and now you can find more instructions there.
Regards...
Responses (2)
-
Accepted Answer
-
Accepted Answer
Figured out it's possible to have predefined colour schemes as it is, but it surely limits the Customizer settings then.
Still, by having only the basics in customizer.json and adding a scheme selection, it's possible. Even though, Customizer generates an error when saving, since it's also saving the select setting to customizer.css - and this is a bug I believe ...
Example:
{
"general": {
"title": "text_general_title",
"description": "text_general_description",
"control": {
"sitename": {
"selector": "#logo a"
}
}
},
"colors": {
"title": "text_colors_title",
"description": "text_colors_description",
"control": {
"container_background-color": {
"type": "color",
"label": "text_colors_container_background_label",
"default": "#bdc3c7",
"selector": "body"
},
"container-color_color": {
"type": "color",
"label": "text_colors_container_color_label",
"default": "#666666",
"selector": "body"
},
"colorscheme": {
"type": "select",
"label": "Colour scheme",
"default": "blue",
"choices": {
"blue": "Blue",
"green": "Green",
"purple": "Purple",
"red": "Red"
},
"selector": "colors"
}
}
},
"images": {
"title": "text_images_title",
"description": "text_images_description",
"control": {
"logo": {
"selector": "#logo a img"
}
}
}
}
Note! The use and point of the defaults in general and images I'm not sure of ...
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »