Ok Lisa looking forwards to have a look when finished.
Yes I know that you have quit RCP, unbelievable that they have not get back to you, that’s why I have decided not to purchase RCP. Support is the most important part, is everything.
So what have you in mind as a replacement?
I don’t know yet. I’ve got @yuzool’s stripe stack http://demo.yuzoolthemes.com/stripe/ for now just so I can take credit cards, but that is a lump sum. I also use a CRM called 17hats.com that I can set up invoices and accept payment through Stripe, the payment service. For now, that is what I am doing.
Your slider didn’t load for me. Also you have some weird Google Font declaration going on See http://d.pr/i/H8JS
You don’t need all of the Raleway sizes I suspect but somehow you have many and 500 is repeated twice.
What browser are you using? Loads for me. I’m still on El Capitan though.
I did see that google font thing… There shouldn’t be 2 copies. The others are italic versions. Will take a closer look.
Raleway:100,100i,200,200i,300,300i,400,400i,500,500i,600,600i,700,700i,800,800i,900,900i" rel=“stylesheet”
Yes I have also the yuzool stacks. Will have a look at the CRM 17hats.com.
Thanks
Just saw that Gary @webdeer is looking at it, he’s the man. His advice worth its weight in gold!!
Regards
In SIteStyles, you should define the paragraph text, as Raleway in one size, and I suggest 400 because I know it exists and is a valid weight. Don’t define any fonts anywhere else until you fix the Raleway font errors. If you define a weight such as 300, and 300 doesn’t exist then it will cause an error.
You can also define a font in ParagraphPro but for your paragraph text you don’t need to. Every extra Google font or any web font will slow the site down, so it is good practice to just use 1 font for all paragraph text and this should be set once in your SiteStyles.
@webdeer thank you, that makes sense. I’ll reset that and republish.
I am going to be using Pro Styles/Section Pro but have yet to figure it out. I think once I can set that up things will be much more organized and stable.
Also, don’t forget about the “Already Loaded” button in ParagraphPro and HeaderPro. This allows you to use a font that you have loaded elsewhere (either in SiteStyles, another font stack or another Paragraph/Header Pro) without making another HTTP call to the Google Fonts CDN
@tav But if I have it on ‘theme default’ in Header Pro, I shouldn’t need to set that? or should I set that anyway? I’m trying to keep things simple and use only 2 fonts, just adjust the sizing as needed.
@webdeer Got rid of everything except 2 fonts and I’m having a hard time getting rid of the error…
This is what I have in my header: family=Allura|PT+Sans" rel=“stylesheet”
You are correct - you only need to use those settings if you are loading a different font for something.
The error is coming because you have pt sans specified as the font for the main body (paragraph) text. Google fonts are case sensitive. Change it to PT Sans as it appears on the Google Fonts website and it should get rid of that error.
Ha. I just did that. Thanks. Republishing now.
I am planning on doing that. Just need to get my Pro Sections/Styles set up 
I will take a look at ghosting as well.
