Bootstrap v4.3 ships with the option to enable responsive font sizes, allowing text to scale more naturally across device and viewport sizes. RFS can be enabled by changing the $enable-responsive-font-sizes Sass variable to true and recompiling Bootstrap.
To support RFS, we use a Sass mixin to replace our normal font-size properties. Responsive font sizes will be compiled into calc() functions with a mix of rem and viewport units to enable the responsive scaling behavior. More about RFS and its configuration can be found on its GitHub repository.
Voting closes in 2 days. Could those of you who have voted for “Payment interactions” explain why that is the single most important feature of Blocs?
I am not clear what the specifics of those “interactions” even are. Are you?
Sure, if I could drop a bric on the page and magically have everything setup for me, automatically (which is only possible if Blocs reads my mind), it would make sense. But surely there will be a lot of setup required, especially for folks who have never taken Payments before, so I really don’t see what the advantage of that new feature is.
Why will “payment interactions” be such a revolutionary feature?
It obviously does not as per the fact I asked. So specifics from you (and not just a link) would be appreciated.
In light of how you reacted to my question, I should add that I am of the STRONG OPINION that there is no stupid question. It clearly is stupid to you, but a soft and kind answer would be a wonderful blessing indeed to me and everyone else who has the same question. But even if I was the lone man on planet earth asking the question, I would still boldly ask that question. A good Q&A is a learning experience that should be treasured, not chastised.
I don’t know, hence my question. But bear in mind I am asking why that feature is winning the vote in light of the fact it is contending with some other very good feature proposals. I want to know why “payment interactions” (whatever that is SPECIFICALLY, I do not know) is so much better than any other feature currently being voted upon. For example, why can’t I add a Paypal link right now? Why the new feature? What does that new feature do for me that I cannot do right now in terms of getting paid via my website?
Option 1: Bric with some most used options, add a button, give id or what parameters the different platforms required. I think @Whittfield and @Norm already talk about this possibility in early posts.
The Option I expect: Buttons and CART LIST from different platforms, EMBED in our webpages…
So with @Eldar tutorials, for layout products and search filters, and with new payment / cart options Embed in our webpage we have “almost” an e-commerce shop.
And probably putting all this together with Volts or a different CMS we can make costumer load and remove the products !!!
This probably is what the users like me wish… @Norm, am I close?
It would be great if Norm can work some magic with implementing a Ecwid store into blocs. The standard embed code from Ecwid is complete bloat and very slow loading; especially the shopping bag code… slow.
@Norm, obviously asset clean up is valuable. Hopefully if it doesn’t make the cut for 4.1 it will for 4.2. Speed and efficiency is the most important part to me. It is usually the most important part of website stickiness and a big part of SEO. That said, if someone is monitizing their website then store performance a lot. Asset reduction is important but fast code (implemented by Blocs) is paramount.
@Pealco
Thank you for providing some clarification! It’s not crystal clear in my mind yet, but it isn’t in your mind either. Basically, you are telling me this fancy new feature MIGHT be a full blown Cart Checkout system. If true, then I can see merit in it. But will it really be that? (Even you said it is ALMOST an e-commerce shop, and that world ALMOST is a big word!) If not a complete Cart Checkout system, is it worth voting for?
In other words, if that feature doesn’t ultimately satisfy the e-commerce requirements of all the people voting for that feature, logic dictates we ought to vote for a different new feature in Blocs.
In other words, we need more information to vote in a truly informed way with regard to “Payment Interactions.” The other 4 voting choices are much more clear. Well, “Prevent layout elements being exported” wasn’t clear until I provided clarity on what it really means, and is why I am currently voting for it.
@JDW Relax, it’s just a vote for a preference and everybody gets a chance to express an opinion in the poll above. It seems pretty obvious your choice is less popular. I guess other users have a different wish list.
How about just all of them if you want a good product? I get the feeling all new features are being implemented as paid add-ons by developers. essential elements for modern websites like filterable galleries are impossible.
Thanks for everyone who took part and casted a vote.
This has been a eye opener, I’m surprised at how many votes the remove unused assets feature got
I’ll try and get as many of these features into v4.1 but I now know what to prioritise
Blocs v4.1 will start its beta testing in January. I’ll also start a separate thread to get more info on what you would like to see added in regards to support for 3rd party e-commerce features.
