Using Ready Theme Shadows Questions

[InvincibleRecordings]

I have been using Miva for a long time and we decided to upgrade to Shadows and are experimenting in a dev store. I hit the ReadyTheme icon and go to Settings Look & Feel. Changing the Default Font does not change anything in the store. Same issue with changing the background color or adding a background image. They do nothing.

[Matt Zimmermann]

The only part in the Look & Feel section of ReadyTheme Settings used in the Shadows ReadyTheme is the Logo Type. To modify the fonts and site background color/image, you would need to update the CSS code found in User Interface -> CSS Resources -> theme-styles

[Bruce - PhosphorMedia]

It's worth reiterating, maybe making this clearer on the actual Shadows promotional pages, that Shadows is a "basic" framework to which, using CSS/HTML you add 'Style' to it. It's not like the other ReadyThemes that you could basically just add products and go. (Other "instant" themes, based on Shadows, is forthcoming.)

[lesliekirk]

It's worth reiterating, maybe making this clearer on the actual Shadows promotional pages, that Shadows is a "basic" framework to which, using CSS/HTML you add 'Style' to it. It's not like the other ReadyThemes that you could basically just add products and go. (Other "instant" themes, based on Shadows, is forthcoming.)

I think you are right Bruce, something needs to be mentioned. I was under the impression that Shadows was a "ready to go" ReadyTheme built on top of Elements, which is not.

[Bruce - PhosphorMedia]

It IS "ready" to go in the same sense as BaseReady theme...which is what we use a starting point when we already have a design we want to implement. So much easier to create a design with these than to repurpose another design to fit.

[lesliekirk]

It IS "ready" to go in the same sense as BaseReady theme...which is what we use a starting point when we already have a design we want to implement. So much easier to create a design with these than to repurpose another design to fit.

I guess some serious "point of clarification" is needed. I equate Elements to the Base ReadyTheme. Shadows according to how I heard it was supposed to have features built on top of Elements. I've even gone so far as to speculate that Elements would be used as the next UI to replace CSSUI (I was close).

It is my understanding that the next ReadyTheme release is supposed to expand upon Elements even further. But the whole purpose of the Evergreen project is to get something that is more plug and play. Something that that would allow you to grab snippets from one ReadyTheme and use it in another. That it would also ensure the coding is standardized across every ReadyTheme going forward. But again, this is just my take on what I was hearing Matt say at the past two conferences.

[GDesigns]

I suppose that could be pointed out on the theme download page. However, we have found that now that the initial 'ground work' is finished, we have a very nice set of add-on features ready to go for Shadows. As Bruce said, it's easier to start with bare bones and make it 'your own', but i agree, as a store owner that wants plug-and-play it's not the way to go.

[William Davis]

I think you are right Bruce, something needs to be mentioned. I was under the impression that Shadows was a "ready to go" ReadyTheme built on top of Elements, which is not.

Ditto! I was under the same erroneous impression. I was planning on switching to Shadows this month, I now may have to reevaluate weather or not is something we are able to do in-house or not.

[lesliekirk]

The only part in the Look & Feel section of ReadyTheme Settings used in the Shadows ReadyTheme is the Logo Type. To modify the fonts and site background color/image, you would need to update the CSS code found in User Interface -> CSS Resources -> theme-styles

The file shows

font-family: "Poppins", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;

but where are those fonts "stored" at?

[Matt Zimmermann]

Hi Leslie,

With the exception of Poppins, the rest are system fonts which are available depending on the OS of the user. Poppins is a Google font and is being called as its own CSS Resource.

[lesliekirk]

Hi Leslie,

With the exception of Poppins, the rest are system fonts which are available depending on the OS of the user. Poppins is a Google font and is being called as its own CSS Resource.

I've started finding where all this stuff is hidden at. It used to be so straight forward

Okay, so I've edited the CSS Resources preconnect-google-fonts. I've also edited the theme-styles to change Poppins to Montserrat

I don't think it's working.

[Matt Zimmermann]

Hi Leslie,

You should not have to modify the path for preconnect-google-fonts, only the path for google-fonts.

[lesliekirk]

Hi Leslie,

You should not have to modify the path for preconnect-google-fonts, only the path for google-fonts.

Well color me confused - so if I just change it in the theme-styles.css it will ignore this?

<link href="https://fonts.googleapis.com/css?fam...at:400,500,700" data-resource-group="css_list" data-resource-code="google-fonts" />

[Matt Zimmermann]

Hi Leslie,

That link loads the font so you can make calls to it in your CSS.

[lesliekirk]

Hi Leslie,

That link loads the font so you can make calls to it in your CSS.

So do I need to edit it? Or leave it alone?