Question:
I’m finding that any paragraph element or rich text element added to our site defaults to the ‘Paragraph 2’ global typography ‘theme’. Our primary paragraph style for our site is ‘Paragraph 1’, with Paragraph 2 and Paragraph 3 being used sparingly in specific instances.
Is there any way to have ‘Paragraph 1’ be the default text theme for any newly added text blocks or elements?
While we know we can obviously change the theme to ‘Paragraph 1’ once the element is added, it’s a hassle and we are concerned our client would sometimes miss this and then the basic typography wouldn’t be as desired. Seems odd that ‘Paragraph 2’ was arbitrarily chosen to be the default…
A very simple and fast solution to this is to save the text style you need in your saved assets. Instead of a quick add, you can drop it from the saved assets. You can also change the style of the para 2 same as para 1 in the website styles.
It’s not just the quick add text box, it’s also happening in rich text boxes in a CMS and other areas.
So if ‘Paragraph 2’ is, and will continue to be, the default applied style for text I guess I’ll have to decide if we want to go through the trouble now of switching my use of Paragraph 1 to Paragraph 2 globally. While we’ve mainly done the Home page already, there are also store items (35+) and a separate CMS collection (100+) :(.
Wish this would have been more clear when starting…
In that case, use the CSS instead, change the font size and weight as you want. For CMS items, the rich content box has its own settings to change all font settings -
Thanks for the response. We’re trying to keep the CSS as minimal as possible where default Wix techniques are available. So to override some ‘Paragraph 1’ elements to be styled as if they were ‘Paragraph 2’ elements might just bring more potential for confusion in the future for the client or any other developer who may have to assist (or even us months/years down the line when we forget ; ). We’ve already switched most of the elements over, just the big CMS collection left to do.
That’s been one of the toughest parts of our introduction to Wix Studio for this project. The CSS access & implementation is not quite 100% there, and since it appears to be such a new thing, nobody seems to know for sure how ‘stable’ some of the classes, rules, techniques may be. We don’t want the site to break months down the line when Wix arbitrarily changes the way they implement something. We’ll see how that goes…
