-
Posts
-
Hi there guys and gals,
A long while back, I left this post detailing how Responsive Text went from being really nice to use (with Visual Composer), to really annoying to use (in Cornerstone). I’d like to follow up on that here, just to sort of bump the discussion and put it back into people’s minds. I really feel, and my clients have been feeling as well, as this would be a far more efficient and effective usage of this functionality.
Placing Responsive Text config options into the customizer would allow us to save page and block templates for later usage, without having to worry about recreating these settings every single page. A site I created recently had a very consistent feel to it, and the client loved it – but they needed their text made in a way for which using Responsive Text was a no-brainer as their answer. The biggest issue here, was that his site was 24 pages… and there was a consistent beginning and ending to nearly every page, in terms of styling. That’s wonderful and all, and it really worked out fast with using custom block templates in Cornerstone to achieve it easily. Unfortunately, 24 times, I had to configure responsive text for these areas, making them exactly the same every single time. What a pain in the ass. Moving this to the customizer would solve every single part of this problem, by allowing people (me) to create the setting how I want it to be for an entire site. That way, my blocks would follow it when imported.
If I need something quick for a single page, then fine, where it is works… but if developers are going to support and push the usage of custom templates for the theme (and plugin, now that CS is it’s own thing), that push for usage should also incorporate convenient usage when taking advantage of other abilities unique to CS. This would be useful for things other than templates as well, because a consistent workflow would likely also involve the memorization of settings used previously, meaning, without thinking about it, I could apply one of my Responsive Text configurations within the CSS field of an element on the fly, without having to recreate it for that new page at all.
This isn’t a request to make things easier with third-parties. This is a request to make things easier with your own custom platform.
I hope this is considered for the future. Thank you for your time.
– Charlie
We certainly appreciate the feedback! This is something we can add to our list of feature requests. This way it can be taken into consideration for future development. All of these items are discussed with our team internally and prioritized based on the amount of interest a particular feature might receive. Thanks!
- <script> jQuery(function($){ $("#no-reply-1066088 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
