Forum Replies Created
- AuthorPosts
You can learn more here http://microformats.org/ and here http://www.w3.org/TR/wai-aria/roles.
Also, in the future, we’ll be improving the structure even more.
Thanks
You’re welcome.
StartupPro already has its own custom options framework, so trying to install an options panel on top would naturally conflict.
What is your ultimate goal? Perhaps we can advise a different route.
Have you tried this plugin?:
Alternatively, if you decide to change your mind about child theming and want to just keep things simple, you can simply paste the following CSS into your theme options (https://startupwp.com/topic/customizing-your-theme/):
@import url(http://fonts.googleapis.com/css?family=Bree+Serif); h1, h2, h3, h4, h5, h6, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a{font-family:'Bree Serif',serif} body, div, p{font-family:arial,sans-serif}
Absolutely, we were going to write the CSS for you and instruct where to paste, but we just needed some more details of what you wanted.
Verdana and Georgia are actually web-safe fonts, widely considered to be installed on most computers, therefore safe to use on the web without needing to install or specially embed the fonts.
Arial and Georgia are widely regarded to have high readability.
Let’s try this and see what you think:
@import url(http://fonts.googleapis.com/css?family=Bree+Serif); h1, h2, h3, h4, h5, h6, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a{font-family:'Bree Serif',serif} body, div, p{font-family:arial,sans-serif}
Since, you’ve decided to use a child theme, we recommend editing style.css in your child theme, which currently looks like this:
/* Theme Name: StartupPro Child Template: startuppro */ @import url("../startuppro/style.css");
Go ahead and update it to:
/* Theme Name: StartupPro Child Template: startuppro */ @import url("../startuppro/style.css"); @import url(http://fonts.googleapis.com/css?family=Bree+Serif); h1, h2, h3, h4, h5, h6, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a{font-family:'Bree Serif',serif} body, div, p{font-family:arial,sans-serif}
You could simply go to Appearance > Editor > style.css from your WP admin and edit it, but we recommend editing it locally and then uploading the updated version via FTP, that way you’ll have a local backup to work with.
See: https://startupwp.com/topic/child-theming/
We recommend using the FileZilla FTP client: http://filezilla-project.org/ / http://wiki.filezilla-project.org/Using
It’s actually already setup this way, you can set your Google fonts above in the options and then type in the Google font’s name below for headers and one other for paragraphs (the main content).
Past that, it’s definitely possible to program in more options, but since you’re already child theming it would easier just to drop the styles in your child theme’s stylesheet.
So looking at [link removed] – Exactly what areas to you want to use what Google fonts?
Thanks
You’re welcome.
Try:
p.wp-caption-text { font-family: arial; font-size: 13px; }
January 23, 2014 at 7:31 AM in reply to: Make content area background transparent, change font color. #1381Great, thanks. Feel free to leave a review here:
January 22, 2014 at 8:44 PM in reply to: Make content area background transparent, change font color. #1379#container { background: transparent; box-shadow: none; }
https://startupwp.com/topic/customizing-your-theme/
Assuming you’ve already set all the non-link text to white in your theme options, what text areas specifically still need styling?
The code has been refined to be a great deal more simple and elegant.
In the case of the comment count, this now simply shows a link to comments if commenting is open and shows nothing if they’re closed.
If you’re comfortable setting up a child theme this is a very easy edit to make:
That’s correct, the options are sufficient for most users, but those requiring more advanced customization definitely want to look into child theming as you’ve done.
Since you’re already child theming, the most direct way (that will take precedence over all other styles) would be to add the following to your child theme’s stylesheet:
@import url(https://fonts.googleapis.com/css?family=Open+Sans); h1, h2, h3, h4, h5, h6, h1 a, h2 a, h3 a, h4 a, h5 a, h6 a{font-family:'Open Sans',sans-serif}
On Google Fonts you can choose different fonts and font weights/styles as well:
https://www.google.com/fonts#UsePlace:use/Collection:Open+Sans
Just to confirm, you’re saying you were now able to fix with a few styles?
Resent
Can we get the link to your website please?
Absolutely, through child theming pretty much anything is possible.
Let us know if you need any help.
1. Currently, the templates only work on individual pages and posts, not site wide.
2. First, make sure that you’ve setup the new pro slider (https://startupwp.com/topic/setting-up-the-slider/). Second, you can adjust the slider settings and change the slider theme and so forth to give the slider arrows, a different look etc.
You’re welcome.
1. First, you’ll need to setup a child theme if you haven’t already:
https://startupwp.com/topic/child-theming/
2. Copy over header.php to the child theme.
3. Open up header.php (https://startupwp.com/topic/understanding-the-theme-code/).
4. Cut the following:
<?php if ( $options['social'] ){ echo '<div id="social">'; if ($options['googleurl']!="") echo '<a href="'.esc_url($options['googleurl']).'" id="social-google"><img src="'.get_template_directory_uri().'/images/social/google.png" alt="Google+" /></a>'; if ($options['linkedinurl']!="") echo '<a href="'.esc_url($options['linkedinurl']).'" id="social-linkedin"><img src="'.get_template_directory_uri().'/images/social/linkedin.png" alt="LinkedIn" /></a>'; if ($options['twitterurl']!="") echo '<a href="'.esc_url($options['twitterurl']).'" id="social-twitter"><img src="'.get_template_directory_uri().'/images/social/twitter.png" alt="Twitter" /></a>'; if ($options['facebookurl']!="") echo '<a href="'.esc_url($options['facebookurl']).'" id="social-facebook"><img src="'.get_template_directory_uri().'/images/social/facebook.png" alt="Facebook" /></a>'; echo ''.do_shortcode( stripslashes(wp_kses_post($options['custicons'])) ).''; echo '</div>'; } ?>
and paste over:
<?php if ( $options['search'] ){ get_search_form(); } ?>
5. Update us at this point, you may require more assistance for styling.
Great, should be a smooth upgrade then.
2. Try clearing all caches while logged out and then restarting your browser and checking. If it’s still there, it’s possible that you actually hard-coded that into the file?
3. Yes, the demo (https://startupwp.com/demo/) has been updated, but you can only mildly see a view visual changes, you won’t be able to see the back-end changes.
What you can do, is download the latest version (from your receipt link) and then open up both your current theme’s and the new theme’s files side-by-side in your favorite text editor and you can then switch back and forth checking out the changes and probably be able to work out fairly easy how to copy customizations over from one file to the other.
Rest assured that 2.0 has been carefully and methodically improved to the point where there should never have to be such a dramatic upgrade again.
Actually, the simplest thing to do here, would be to upgrade to Pro because the custom templates are possible for posts in Pro, so you’d be able to have two sidebars right on articles.
However, important note, we’ve just updated to version 2.0. While all your theme options should port over nicely, the theme file code itself has been greatly improved, so could pose a problem if you’ve made any advanced customizations.
The design has also been mildly reworked as well, have a look:
If you want to test it out, you have 60 days to request a full refund.
Thanks
2. You’re only seeing this because you’re logged in with your account, other people can’t see this. Also, we recommend not disabling right-click. Anyone that wants to get around this can, and it only manages to annoy legitimate users.
3. Yes. Because the code has changed so much (for the better mind you) it simply won’t match up from the child theme anymore. We definitely advise checking out version 2.0 separately, almost best to consider it a completely different theme. We’ll continue to support version 1.0, but 2.0 is much improved.
- AuthorPosts