<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums User Favorites: DanteHamilton</title>
		<link><a href='https://legacy.forums.gravityhelp.com/profile/dantehamilton'>dantehamilton</a></link>
		<description>Gravity Support Forums User Favorites: DanteHamilton</description>
		<language>en-US</language>
		<pubDate>Wed, 15 Apr 2026 01:20:51 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/profile/" rel="self" type="application/rss+xml" />

		<item>
			<title>Kevin Flahaut on "Styling GF in version 1.5 - best practice?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/styling-gf-in-version-15-best-practice#post-15063</link>
			<pubDate>Mon, 27 Dec 2010 17:18:59 +0000</pubDate>
			<dc:creator>Kevin Flahaut</dc:creator>
			<guid isPermaLink="false">15063@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Better CSS specificity will usually do the trick for you. Instead of just..&#60;/p&#62;
&#60;p&#62;&#60;code&#62;.gfield {margin:10px}&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;you go with something more specific like this&#60;/p&#62;
&#60;p&#62;&#60;code&#62;body .gform_wrapper ul.gform_fields li.gfield {margin:10px}&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;If done right, in many cases better specificity will override an &#34;!important&#34; statement.&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.smashingmagazine.com/2010/04/07/css-specificity-and-inheritance/&#34; rel=&#34;nofollow&#34;&#62;http://www.smashingmagazine.com/2010/04/07/css-specificity-and-inheritance/&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;Of course, you can always still copy the ready class styles from the plugin style sheet and incorporate those into your new ones if you still want turn off the CSS output.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Luke on "Styling GF in version 1.5 - best practice?"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/styling-gf-in-version-15-best-practice#post-15062</link>
			<pubDate>Mon, 27 Dec 2010 16:50:06 +0000</pubDate>
			<dc:creator>Luke</dc:creator>
			<guid isPermaLink="false">15062@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I've recently created a couple themes and have included custom styles for Gravity Forms. However, it required the user to turn off CSS output in the GF Forms Settings. With GF 1.5, there are some handy features with the CSS Ready Classes. Turning off the output, turns these off as well.&#60;/p&#62;
&#60;p&#62;My question I guess is to ask what people have found to be the best way to style gravity forms without turning off CSS Output while also not having to add &#34;!important&#34; markup all over the stylesheet? Best practices?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
